Refine bounded traversal contracts

docs/COMPATIBILITY.md

@@ -68,7 +68,8 @@ Milestone 0 preserves:
 - Edge schema version 1.
 - Changeset schema version 1.
 - Result-envelope schema version 1.
-- SQLite index schema version 2.
+- SQLite index schema version 3. Version 2 indexes remain disposable and automatically rebuild;
+  version 3 adds a source-ordered incoming-edge index for bounded impact traversal.
 - Index-attestation schema version 1.
 - Incremental extraction-cache schema version 1.
 

docs/MCP_CONTRACT.md

@@ -38,6 +38,11 @@ returns the complete fixed binding, active index path, proposal and application
 recommended workflow. `docforge_sync` exposes the same idempotent synchronization explicitly.
 Neither operation changes canonical sources.
 
+Search, filter, backlinks, dependencies, and impact accept explicit result limits bounded by the
+project `max_results` policy. Omitted limits are still capped. Collection responses report whether
+they were truncated. Traversal also reports whether truncation came from the result limit or its
+deterministic candidate-edge work budget; it does not scan or materialize the complete edge table.
+
 Adapter-backed servers also validate their process-start implementation fingerprint before every
 tool. `adapter_restart_required` is stale but not synchronizable. Its remediation is
 `restart_project_server`; the current process does not reload project code, update Git staging, or

docs/USER_MANUAL.md

@@ -463,9 +463,9 @@ validate-index
 show NODE_ID
 search QUERY [--limit N]
 filter [--family X] [--authority X] [--status X] [--tag X] [--limit N]
-backlinks NODE_ID [--relation RELATION]
-dependencies NODE_ID [--depth N]
-impact NODE_ID [--depth N]
+backlinks NODE_ID [--relation RELATION] [--limit N]
+dependencies NODE_ID [--depth N] [--limit N]
+impact NODE_ID [--depth N] [--limit N]
 context PROFILE [--budget N]
 ```