Complete DFG-8 adapter proposal support

SLICE_HISTORY.md

@@ -326,3 +326,43 @@ quality and a documented rollback path.
 
 DFG-8: adopt isolated AssetForge-only proposals with explicit review and the canonical Worldforge
 build and verification workflow.
+
+## DFG-8 AssetForge proposal adoption
+
+### Changed
+
+- Added confined adapter proposal settings for canonical sources, writer permissions, changesets,
+  templates, previews, and declared review output.
+- Added a project-owned proposal-validation hook while retaining generic hash, permission, graph,
+  conflict, atomic-storage, diff, and preview enforcement in the core.
+- Moved generic Markdown and TOML source-layout validation behind the generic project owner so an
+  adapter can enforce its own canonical format without weakening graph validation.
+- Added an explicit full-surface server constructor for one configured project service and one
+  startup-bound writer.
+- Marked base, content, source, adapter-source, and index conflicts as stale tool results.
+- Released the proposal-enabled adapter boundary as DocForge 0.6.0.
+
+### Verification
+
+- OpenClaw was bound to the AssetForge-only session and update-only permission.
+- One real proposal updated an existing AssetForge chapter, validated, produced a structured diff,
+  and rendered an isolated escaped preview before manual integration.
+- The Worldforge canonical builder and manual index rebuilt after review. The original changeset
+  then failed with `base_conflict` against the new canonical source hash.
+- Live tests rejected create, metadata, root-manifest, relationship, and cross-family access;
+  rejected an overlapping changeset; escaped raw HTML; preserved canonical bytes; and rejected
+  stale canonical sources.
+- The complete DocForge and Worldforge manual suites, shadow proof, generated-output check, format,
+  and lint passed.
+
+### Limits
+
+- DFG-8 permits content-only updates to existing AssetForge chapters. Create, move, delete,
+  metadata, relationship, and manifest changes remain closed.
+- DocForge does not apply canonical changes, run the Worldforge builder, use Git, deploy, or publish.
+- A developer must review and manually integrate accepted prose.
+
+### Next gate
+
+DFG-9: decide from evidence whether a narrowly scoped developer-only application command is
+justified or manual integration should remain permanent.