Close Milestone 4 with adapter adoption evidence

docs/MCP_CONTRACT.md

@@ -28,6 +28,30 @@ Bootstrap and contract results include `effective_policy` schema version 1 plus
 registered surface and startup-bound proposal/application access. The project descriptor remains
 schema version 1 and does not silently acquire machine-specific process policy.
 
+## Fixed reference binding
+
+`docforge.reference_mcp` is the fixed runnable binding for the in-repository Python, JavaScript,
+TypeScript, and C++ reference adapters:
+
+```bash
+python -I -m docforge.reference_mcp \
+  --project-root /absolute/project \
+  --capability-mode read
+```
+
+It loads only `.docforge/reference-adapter.toml`, selects only the fixed provider for the declared
+language, and constructs the same project-bound read surface through `create_read_only_server()`.
+Bootstrap binding metadata includes `server_module = "docforge.reference_mcp"`,
+`adapter_mode = "reference"`, the selected `reference_language`, and the exact
+`reference_config_hash`.
+
+The reference command accepts read capability mode only. It registers all 21 read tools below and
+no isolated proposal or canonical-application tools. The configuration cannot select a provider,
+module, command, arguments, working directory, environment, or arbitrary discovery behavior. See
+[Reference Adapters](REFERENCE_ADAPTERS.md) for language scope and
+[Agent Integration](AGENT_INTEGRATION.md) for the immutable launcher and generated client
+fragments.
+
 ## Read tools
 
 - `docforge_bootstrap`
@@ -45,6 +69,8 @@ schema version 1 and does not silently acquire machine-specific process policy.
 - `docforge_get_task_context`
 - `docforge_validate_project`
 - `docforge_render_status`
+- `docforge_graph_plan`
+- `docforge_graph_render_status`
 - `docforge_visualize`
 - `docforge_stop_visualization`
 - `docforge_visualization_status`
@@ -349,3 +375,6 @@ permissions and project instructions remain responsible for that broader boundar
 The legacy `adapter_policy` object remains byte-compatible. It is now a projection of the
 versioned `effective_policy`; `--no-ast` restrictively overrides adapter evolution, AST analysis,
 and Logic indexing without widening any other capability.
+
+See [Legacy Adapters and No-AST Policy](LEGACY_AND_NO_AST.md) for the compatibility boundary and
+why the AST and Tree-sitter reference adapters are not no-AST adapters.