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

Complete DFG-8 adapter proposal support

Browse source
This commit is contained in:
Andraxion 2026-07-22 11:50:49 -04:00
parent f1e31487c0
commit 591bf0ae7d
14 changed files with 525 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/CONTRACT.md
View file

@ -1,4 +1,4 @@
# DocForge 0.5 contract
# DocForge 0.6 contract
## Authority boundary
@ -18,7 +18,7 @@ commit when Git is available; it cannot change repository state.
- Result envelope: `schemas/result.schema.json`, version 1.
- Changeset schema: `schemas/changeset.schema.json`, version 1.
- Index schema: version 1, disposable and reproducible.
- Core, CLI, and MCP server: version 0.5.0.
- Core, CLI, and MCP server: version 0.6.0.
Schema files describe the generic interchange contract. Runtime validation remains responsible for
path confinement, source hashing, relationship resolution, dependency cycles, project limits, stale
@ -94,3 +94,14 @@ process. A project integration may explicitly construct a read-only MCP server f
`ProjectService` and an optional project-owned context provider. That server exposes only the fixed
read tool surface. The core does not discover adapters, choose projects or sessions, or import
project policy.
A proposal-enabled adapter declares confined canonical source, changeset, template, preview, and
render paths plus fixed writer permissions. It must supply a proposal validator. The core continues
to enforce optimistic hashes, writer permissions, graph integrity, limits, atomic changeset storage,
conflict detection, and preview confinement. The adapter validator enforces source-format and
project semantics that the generic core cannot infer. Generic projects retain the built-in Markdown
and TOML source-layout validator.
An explicit integration may construct the full fixed MCP surface for a configured adapter project
and one startup-bound writer. This does not add adapter discovery or canonical application. An
adapter without proposal settings or validation remains read-only.

5
docs/MCP_CONTRACT.md
View file

@ -26,6 +26,11 @@ construct the same read-only surface from a validated `ProjectService` and proje
provider. This form cannot register proposal tools. Project discovery, session selection, family
partitioning, and custom context policy remain outside the DocForge core.
An explicit project integration may construct the full fixed surface only after supplying a
confined proposal policy and startup-bound writer. Adapter proposal validators may narrow the
writer's declared operations further. They cannot add tools, weaken core changeset validation, or
enable canonical application.
## Isolated proposal tools
- `docforge_create_changeset`