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

feat: add isolated proposal changesets

Browse source
This commit is contained in:
Andraxion 2026-07-22 02:58:51 -04:00
parent 9702ed1265
commit 8c75f4f44d
22 changed files with 2314 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -9,8 +9,9 @@ project commands, or perform Git and deployment operations.
## Current gate
DFG-1 and DFG-2 are complete. DFG-3 is the active gate: isolated changesets for structured create,
update, move, and delete proposals. Canonical writes remain closed.
DFG-1 through DFG-3 are complete. DFG-4 is the active gate: deterministic previews and renderer
orchestration over validated project data. Canonical application remains external and closed to the
normal MCP server.
## Development
@ -18,7 +19,13 @@ update, move, and delete proposals. Canonical writes remain closed.
uv sync
uv run python -m unittest discover -s tests -v
uv run docforge --project-root tests/fixtures/alpha validate
uv run docforge-mcp --project-root tests/fixtures/alpha --proposal-writer alpha-editor
```
The command prints deterministic JSON. Derived indexes live under each project's configured cache
directory and are never canonical input.
Proposal writers are declared by ID in `.docforge/project.toml`. Each writer receives explicit node
families and operation types. The MCP process binds to one writer at startup; tools cannot select or
impersonate another writer. Create, update, move, and delete tools write only isolated JSON
changesets below the configured changeset root.