Why

The memories MCP search tool previously stopped once it hit max_results, so callers could tell there were more matches via truncated but had no way to fetch the rest of the result set. That made large searches awkward for clients that need to keep paging through a stable, deterministic view of the matches.

What changed

• add an optional cursor field to SearchMemoriesRequest / tool input and return next_cursor in SearchMemoriesResponse
• update the MCP schemas and tool wiring so clients can request subsequent pages explicitly
• change the local memories backend to collect and sort the full scoped match list, then slice the requested page and reject invalid cursors
• add unit coverage for paginated search results and invalid cursor handling in memories/mcp/src/local_tests.rs

Testing

• Added targeted unit coverage in memories/mcp/src/local_tests.rs
• GitHub Actions are running for the branch