Bug Report: Waypoint Trait Filter Returns Incorrect Results #111

Using the generated axios client as described in the docs.

Endpoint: GET /v2/systems/{systemSymbol}/waypoints?traits=SHIPYARD

Issue: The traits query parameter filter returns waypoints that do NOT have the requested trait, while missing waypoints that DO have the trait.

Steps to Reproduce:

Call GET /v2/systems/X1-NA27/waypoints?traits=SHIPYARD
API returns 10 waypoints: X1-NA27-A1, X1-NA27-DX5D, X1-NA27-B6, X1-NA27-B7, X1-NA27-B8, X1-NA27-B9, X1-NA27-B10, X1-NA27-B11, X1-NA27-B12, X1-NA27-B13
Inspect the traits array of each returned waypoint
Expected Behavior:
Only waypoints with SHIPYARD in their traits array should be returned.

Actual Behavior:

None of the 10 returned waypoints have the SHIPYARD trait
They have other traits like MARKETPLACE, COMMON_METAL_DEPOSITS, BARREN, etc.
Waypoint X1-NA27-H51 (confirmed to have SHIPYARD trait when fetched individually) is NOT included in the results
Example Response Data:

X1-NA27-A1 traits: BARREN, OUTPOST, SCARCE_LIFE, ASH_CLOUDS, MAGMA_SEAS, MARKETPLACE ❌ No SHIPYARD
X1-NA27-DX5D traits: COMMON_METAL_DEPOSITS, STRIPPED, MARKETPLACE ❌ No SHIPYARD
X1-NA27-B6 traits: MARKETPLACE ❌ No SHIPYARD
(Same pattern for all 10 waypoints - none have SHIPYARD)
Impact:
The trait filter is completely unreliable. Clients must fetch all waypoints and filter client-side as a workaround.

API Version: 2.3.0