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

feat: add adapter read-only MCP boundary

Browse source
This commit is contained in:
Andraxion 2026-07-22 05:59:20 -04:00
parent 1943c36ef3
commit f1e31487c0
17 changed files with 209 additions and 45 deletions
Download patch file Download diff file Expand all files Collapse all files

38
SLICE_HISTORY.md
View file

@ -288,3 +288,41 @@ DFG-6: prove the generic core with an unrelated project and simultaneous project
DFG-7: adopt project-bound DocForge retrieval for real Worldforge read-only tasks with measured
quality and a documented rollback path.
## DFG-7 Worldforge read-only adoption
### Changed
- Added an explicit adapter-backed read-only MCP constructor that accepts one validated project
service and an optional project-owned context provider.
- Kept adapter discovery, session selection, family partitioning, and project context policy outside
the generic core.
- Added Worldforge-owned descriptors and separate Worldforge and AssetForge sessions with disjoint
derived indexes and the exact fixed read tool surface.
- Added durable retrieval, context-size, omission, latency, stale-state, and rollback evidence.
- Released the adapter-backed read-only boundary as DocForge 0.5.0.
### Verification
- Eight real Worldforge and AssetForge retrieval tasks retained every required node in the first
five results; seven matched the current manual index result set exactly.
- Active and Phase 5 contexts reduced the full structured Worldforge session by 97.3% and 98.2%.
Tight budgets reported every omitted candidate.
- Two simultaneous MCP processes retained separate identities, exposed only read tools, rejected
cross-family node access, and kept Worldforge stale-state failure isolated from AssetForge.
- Checked DocForge search measured 84.4 ms median in the adoption run versus 18.8 ms for the current
manual index. The additional validation cost remained below 0.1 seconds.
- The DocForge suite, Worldforge manual suite, integration tests, shadow proof, format, lint, and
generated-output checks passed.
### Limits
- DocForge read-only operations do not write canonical Worldforge files or replace its builder.
- Adapter-backed read-only service construction is explicit; the generic server does not discover
project adapters or sessions.
- AssetForge proposal access, canonical application, publication, and deployment remain closed.
### Next gate
DFG-8: adopt isolated AssetForge-only proposals with explicit review and the canonical Worldforge
build and verification workflow.