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

Record Milestone 0 performance baseline

Browse source
This commit is contained in:
Andraxion 2026-07-29 03:20:09 -04:00
parent fd4759096e
commit cb59a822a8
5 changed files with 542 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

19
ACTIVE_SLICE.md
View file

@ -1,15 +1,12 @@
# Active slice
# Active milestone
```text
Slice: DFG-23 process-stable adapter implementation boundary
Goal: Prevent a long-running project server from synchronizing with adapter code or configuration that changed after the adapter object was imported.
In scope: Language-neutral implementation roots/files/suffixes; project-local Python package inference; descriptor fingerprinting; bounded change evidence; restart-required MCP remediation; staged/unstaged deletion contract guidance.
Out of scope: In-process Python module reloading; MCP self-restart; project-specific Git enumeration; canonical source mutation; deployment or publication.
Done when: Every MCP operation rejects added, changed, deleted, missing, or unsafe adapter implementation files before synchronization; derived files outside the declared boundary remain ignored; descriptor changes require restart; deletion semantics remain manifest-owned and staging-independent; the complete DocForge quality gate passes.
Owners: DocForge owns implementation-boundary confinement, fingerprinting, bounded diagnostics, MCP preflight, and restart remediation. Adapters own the declared boundary and current source-manifest enumeration. Canonical sources and Git staging remain outside this lifecycle guard.
Proof: The focused adapter suite passed 15 tests, including inferred and explicit implementation boundaries, descriptor changes, additions, edits, deletions, ignored derived files, and exact MCP remediation. Strict Pyright passed with no errors or warnings. Ruff lint and formatting, Python compilation, and the HTML/CSS/JavaScript quality gate passed. The complete warning-strict suite passed 87 tests and 2 subtests.
Milestone: 0 — successor foundation and measured baseline
Goal: Seed DocForge2 from the most advanced local lineage without breaking DocForge v1 contracts.
In scope: Complete Git lineage; verified no-AST work; adapter lifecycle safeguards; compatibility guarantees; repository-native contract and quality gates; cold/warm, memory, rendering, and response-size baselines; public successor migration; fresh-clone verification.
Out of scope: Storage redesign; compiler or renderer redesign; portable render plans; self-hosting; production MCP repointing; WorldForge or ScrapeStation changes; tags and releases.
Done when: administrator/DocForge2 is public and seeded from the advanced clean tree; administrator/DocForge remains intact; origin and legacy identify the successor and v1 remotes; all gates and a fresh-clone proof pass; the recorded baseline identifies measured bottlenecks without speculative optimization.
Status: Candidate. Source integration, contracts, gates, and measurements are complete. Public repository creation, remote migration, and fresh-clone verification remain.
```
**Next gate:** Prove Worldforge's C++ integration against the generic incremental and assembly
contracts. Extract a reusable language frontend only after a second consumer demonstrates which
behavior is genuinely shared.
No later milestone is active.