Close Milestone 2 with measured evidence

README.md

@@ -13,6 +13,10 @@ declared manuals, visualizes project structure, and manages reviewable documenta
   continuation.
 - Records one bounded, versioned latest-generation graph transition without creating a history
   database.
+- Generates deterministic project-bound Codex, Claude, and OpenClaw client fragments without
+  copying ambient secrets.
+- Diagnoses one client binding through bounded read-only checks without starting MCP or rebuilding
+  project state.
 - Automatically synchronizes disposable indexes before MCP work.
 - Creates, validates, diffs, and previews isolated changesets.
 - Registers complete proposals atomically without caller-managed hash chaining.
@@ -135,6 +139,16 @@ Start an MCP server for one project:
 Add `--canonical-applier project-editor` only when that MCP integration should expose the
 hash-bound `docforge_apply_changeset` tool.
 
+Preview a read-only Codex fragment and diagnose an installed binding:
+
+```bash
+.venv/bin/docforge configure codex --project "$PROJECT"
+.venv/bin/docforge doctor --client codex --project "$PROJECT"
+```
+
+Pass `--output /absolute/path/docforge.toml` only when creating a standalone fragment. DocForge
+never replaces or merges an existing different client file.
+
 For an unconfigured codebase, begin with a read-only language and documentation assessment:
 
 ```bash
@@ -156,6 +170,10 @@ DocForge describes them as a source graph.
   performance, memory, rendering and response sizes, bottlenecks, and missing coverage.
 - [Milestone 0 closeout](docs/MILESTONE_0_CLOSEOUT.md) — lineage, migration, security scan,
   repository state, and fresh-clone proof.
+- [Milestone 2 baseline](docs/MILESTONE_2_BASELINE.md) — task context, generation diff, client
+  configuration, doctor, response-size, counter, and memory measurements.
+- [Milestone 2 closeout](docs/MILESTONE_2_CLOSEOUT.md) — implemented contracts, adversarial
+  validation, exclusions, and exact candidate evidence.
 - [MCP contract](docs/MCP_CONTRACT.md) — exact tool and process boundary.
 - [Viewer manager](docs/VIEWER_MANAGER.md) — native service setup and lifecycle.
 - [Adapter decision](docs/APPLICATION_DECISION.md) — why custom adapters own canonical
@@ -178,7 +196,7 @@ make gate
 
 Focused entry points are available as `make contract`, `make test`, `make type`,
 `make benchmark-smoke`, `make benchmark`, `make benchmark-m1-smoke`, and
-`make benchmark-m1`.
+`make benchmark-m1`. Milestone 2 adds `make benchmark-m2-smoke` and `make benchmark-m2`.
 
 The committed 1,000-node baseline and its measurement method are under `benchmarks/`.