administrator/DocForge2
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

feat: add project adapter shadow contract

Browse source
This commit is contained in:
Andraxion 2026-07-22 04:17:05 -04:00
parent 411f417670
commit 561d98f1f8
10 changed files with 532 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -10,9 +10,11 @@ isolated previews through the explicit render boundary.
## Current gate
DFG-1 through DFG-4 are complete. DFG-5 is the active gate: a shadow-only Worldforge adapter that
must reproduce current semantics and output without changing the live workflow. Canonical
application remains external and closed to the normal MCP server.
DFG-1 through DFG-4 are complete. DFG-5 is the active gate. Its first shadow proof maps the
non-AssetForge Worldforge graph through the standard index boundary and verifies project-specific
queries, active and phase contexts, and 31 unaffected generated outputs. The independently managed
AssetForge family and the combined manual page remain excluded until that content is explicitly in
scope. Canonical application remains external and closed to the normal MCP server.
## Development
@ -37,3 +39,9 @@ Projects may also declare render views with confined template, preview, and outp
built-in renderer converts CommonMark to escaped HTML through strict template tokens. MCP may render
validated changesets only into isolated preview paths. Declared project output is generated through
the explicit local CLI command and is never an MCP operation.
Project adapters implement `AdapterLoader` and return one ordered, immutable `AdapterProjection`.
`AdapterProject` validates the projection and exposes it through the same disposable index used by
generic projects. Project-specific context, query ordering, and render-model policy remain in the
adapter. Shadow adapters are local integration tools; the normal MCP server does not discover or
execute them.