Please fix the published OpenAPI spec to declare the query parameters the API supports

We build spec‑driven integrations against the Aha! REST API (OpenAPI codegen, LLM tool frameworks). These clients can only send parameters the published openapi.json​ declares.

The gap is API‑wide, not endpoint‑specific: the spec omits query parameters the API actually supports and that you document on aha.io/api — notably sparse fieldsets (`fields`), and per‑resource filters. Because they aren't in the spec, standards‑based clients can't paginate, select fields, or filter — even though the live API honors all of them. The only workaround today is each integrator maintaining a patched copy of your spec.

Please update the published spec so it declares the query parameters each endpoint actually supports (fields​ across resources, and the documented per‑resource filters). If the spec is generated from the API, please include the parameter definitions in that generation so it stays complete going forward.