Problem
Developer search lacks a stable and deterministic pagination mechanism. Clients need a predictable cursor-based API and MCP contract that can survive reordering and invalid or expired continuations without exposing unstable internal indexes.
Proposed solution
Implement stable cursor pagination for developer search which uses an opaque continuation token, deterministic ordering, and bounded page sizes. The contract should define max 20 results, invalid cursor handling, and expiration behavior in both API and MCP layers.
Acceptance criteria
- Opaque continuation token in API and MCP.
- Deterministic ordering across repeated requests.
- Max result size of 20.
- Explicit behavior for invalid, expired, or stale tokens.
- Test coverage for ordering and continuation edge cases.
- Documentation for client migration and retry behavior.
Privacy and trust
Continuation tokens must not encode sensitive developer profile content or raw queries. The system must treat cursor state as opaque and safe to store only as a server-managed token.
Dependencies
- Search ordering model and query execution.
- API and MCP contract updates.
- Test infrastructure for cursor lifecycle behavior.
Problem
Developer search lacks a stable and deterministic pagination mechanism. Clients need a predictable cursor-based API and MCP contract that can survive reordering and invalid or expired continuations without exposing unstable internal indexes.
Proposed solution
Implement stable cursor pagination for developer search which uses an opaque continuation token, deterministic ordering, and bounded page sizes. The contract should define max 20 results, invalid cursor handling, and expiration behavior in both API and MCP layers.
Acceptance criteria
Privacy and trust
Continuation tokens must not encode sensitive developer profile content or raw queries. The system must treat cursor state as opaque and safe to store only as a server-managed token.
Dependencies