Follow-up to #38.
PageArgs::resolve applies one global pagination policy (defaults, clamp to 1..=100), but several endpoints have their own bounds the declarations don't express:
GET /v2/issues clamps count to a minimum of 5
GET /revisions/{locator}/snippets caps pageSize at 50 (currently enforced ad hoc in the Snippet list_page impl)
Idea: encode per-entity bounds in the param structs / declarations themselves so that
- both surfaces enforce the same bounds,
- the MCP input schemas advertise them (agents see constraints instead of discovering them via API errors), and
--help makes the CLI act as documentation for what each endpoint supports.
Not needed for #38 — deliberately deferred.
Follow-up to #38.
PageArgs::resolveapplies one global pagination policy (defaults, clamp to 1..=100), but several endpoints have their own bounds the declarations don't express:GET /v2/issuesclampscountto a minimum of 5GET /revisions/{locator}/snippetscapspageSizeat 50 (currently enforced ad hoc in theSnippetlist_pageimpl)Idea: encode per-entity bounds in the param structs / declarations themselves so that
--helpmakes the CLI act as documentation for what each endpoint supports.Not needed for #38 — deliberately deferred.