Establish Milestone 0 compatibility and quality gates

README.md

@@ -86,8 +86,8 @@ hiding a step inserts an explicit omitted-path bridge so downstream control flow
 Requirements are Python 3.12+, `uv`, and Node.js/npm.
 
 ```bash
-git clone forgejo@repo.andraxion.net:administrator/DocForge.git /absolute/path/DocForge
-cd /absolute/path/DocForge
+git clone forgejo@repo.andraxion.net:administrator/DocForge2.git /absolute/path/DocForge2
+cd /absolute/path/DocForge2
 uv sync --group dev
 npm ci
 
@@ -129,6 +129,8 @@ DocForge describes them as a source graph.
 - [User manual](docs/USER_MANUAL.md) — features, setup, visualization, CLI, MCP, apply, adapters,
   and troubleshooting.
 - [Core contract](docs/CONTRACT.md) — invariants and security boundary.
+- [Milestone 0 compatibility](docs/COMPATIBILITY.md) — preserved package, CLI, MCP, adapter,
+  schema, changeset, rendering, and no-AST guarantees.
 - [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
@@ -143,13 +145,13 @@ DocForge describes them as a source graph.
 
 ## Development
 
+Run the complete repository-native gate:
+
 ```bash
-npx pyright
-npm run lint:web
-uv run ruff check src tests tools
-uv run ruff format --check src tests tools
-uv run python -m compileall -q src tests tools
-uv run pytest -q
+make gate
 ```
 
+Focused entry points are available as `make contract`, `make test`, `make type`,
+`make benchmark-smoke`, and `make benchmark`.
+
 See [AGENTS.md](AGENTS.md) before changing core boundaries.