Ruleset: paginated operations must use the cursor shape #18

What to build

A conditional rule: an operation that paginates must paginate the estate way.

This deliberately does not require every collection to paginate. Bounded collections stay as plain arrays. The rule only fires when an operation shows signs of paging, and then insists on the cursor convention rather than any of the alternatives.

Acceptance criteria

• An operation with a bare limit and no cursor fails the check
• An operation returning a plain array with no paging parameters passes
• The paginated collections in the estate pass when the rule merges
• The rule is shown to fail against a deliberately bad fixture

Blocked by

• Add vacuum lint inputs and a ruleset requiring operationId
• Add cursor pagination to chat sessions and messages (agents-api)
• Add cursor pagination to note listings (knowledge)