Add versioned effective policy

docs/COMPATIBILITY.md

@@ -35,6 +35,7 @@ remain supported:
 - `docforge.index`
 - `docforge.mcp_server`
 - `docforge.models`
+- `docforge.policy`
 - `docforge.render_contract`
 
 Names beginning with an underscore are implementation details. New public names may be added
@@ -72,6 +73,8 @@ Milestone 0 preserves:
   version 3 adds a source-ordered incoming-edge index for bounded impact traversal.
 - Index-attestation schema version 1.
 - Incremental extraction-cache schema version 1.
+- Effective process-policy schema version 1. The project descriptor remains schema version 1;
+  machine-specific capability selection is a startup binding, not canonical project content.
 - Read-pagination schema version 1. Existing tool names and required arguments are unchanged.
   Context and changeset MCP reads accept optional limits and opaque generation-bound cursors.
   Direct Python changeset methods and the ordinary CLI context command retain full legacy results
@@ -112,6 +115,10 @@ The binding:
 - Applies the same restriction during hash-bound canonical-application refresh.
 - Reports the effective policy through bootstrap and contract results.
 
+The legacy `adapter_policy` payload and error codes remain unchanged. The version-1
+`effective_policy` is additive and makes precedence, capability mode, render behavior, blocked
+tools, and prohibitions machine-readable.
+
 DocForge does not inspect arbitrary adapter source to prove which parser implementation it uses.
 The no-AST binding is an owner-selected process policy backed by Logic publication and retrieval
 enforcement. It is not a filesystem sandbox and cannot stop an unrelated process with repository