feat(pagination): surface cursor data to proto, and raw + llm formatters

Summary

Part of #248 (closed), depends on !698 (merged). This MR surfaces cursor pagination metadata to all consumers — proto, JSON body (RAW), and GOON (LLM) formats — so agents always know whether more pages exist regardless of how they consume the response.

What the agent sees

When a query includes a cursor, the response now contains pagination info in two places:

Proto metadata (gRPC consumers):

QueryMetadata {
    row_count: 20,
    pagination: PaginationInfo { has_more: true, total_rows: 85 }
}

JSON response body (RAW and LLM/GOON formats):

{
    "query_type": "search",
    "nodes": [...],
    "edges": [],
    "pagination": {
        "has_more": true,
        "total_rows": 85
    }
}

When the query has no cursor, pagination is absent from both — non-paginated queries are unchanged.

Edited by Michael Usachenko

Merge request reports

Loading
Loading