find: has_more_results computed but not exposed on FindOutput (pagination contract gap)

[HumanBean17]

Summary

find_v2 computes has_more_results for pagination signaling and places it in the hints payload, but FindOutput has no such field, so MCP clients never learn whether more pages exist.

Evidence (confirmed)

mcp_v2.py:1055 computes has_more_results; :1066 puts it in the hint payload; FindOutput has no has_more_results field. The same gap exists on neighbors (no has-more signal at all).

Impact

An LLM paging through find can't tell if it reached the end without an extra probe call. The data is computed and then dropped from the contract.

Suggested fix

Add has_more_results: bool | None = None to FindOutput (and consider NeighborsOutput).