Complete DFG-8 adapter proposal support

README.md

@@ -10,11 +10,12 @@ isolated previews through the explicit render boundary.
 
 ## Current gate
 
-DFG-1 through DFG-7 are complete. Worldforge now uses two explicit read-only sessions for its main
-documentation and AssetForge documentation. Real-task retrieval, bounded context, cross-session
-isolation, stale-state rejection, and rollback to the existing manual index are measured. DFG-8 is
-the active gate: allow AssetForge-only proposals through a separate reviewed changeset workflow.
-Canonical application remains external and closed to MCP.
+DFG-1 through DFG-8 are complete. Worldforge uses separate read-only sessions and an optional
+AssetForge-only proposal process. OpenClaw can update existing AssetForge chapter prose through
+isolated, validated changesets and escaped previews; canonical integration remains a developer
+review step through Worldforge's established builder. DFG-9 is the active gate: decide from recorded
+evidence whether any developer-only application command is justified. Canonical application remains
+external and closed to MCP.
 
 ## Development
 
@@ -46,3 +47,8 @@ generic projects. Project-specific context, query ordering, and render-model pol
 adapter. Shadow adapters are local integration tools; the normal MCP server does not discover or
 execute them. An explicit integration may bind a validated adapter project to DocForge's read-only
 MCP surface without enabling proposal tools.
+
+Proposal-enabled adapters supply confined project settings and a project-owned validator. The core
+still owns hashes, permissions, changeset storage, conflict checks, graph validation, diffs, and
+preview confinement. The adapter owns source-format rules and may only narrow the allowed proposal
+surface.