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

Add deterministic client integration diagnostics

Browse source
This commit is contained in:
Andraxion 2026-07-29 10:15:27 -04:00
parent eb9355b003
commit fb0df5e4a1
15 changed files with 6193 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

13
ACTIVE_SLICE.md
View file

@ -6,11 +6,14 @@ Goal: Let one project-bound server return compact, task-shaped, explainable cont
In scope: Capability modes; capability-aware bootstrap; versioned retrieval plans and context capsules; task-shaped context; generation diffs; evidence-gap diagnostics; generated client configuration; doctor checks.
Out of scope: Independent render-plan packages; adapter SDK expansion; self-hosting; storage replacement; embeddings; WorldForge or ScrapeStation changes; production MCP repointing; tags and releases.
Done when: Policy and capabilities are explicit; bootstrap recommends only available actions; task context is compact, deterministic, provenance-bearing, and bounded; generation and evidence gaps are explainable; generated configuration and doctor checks are safe and tested; the complete repository gate and Milestone 2 benchmark pass.
Status: Active. Effective policy and versioned task retrieval are committed. The latest-generation
diff receipt is implemented with focused contract, failure, CLI, MCP, legacy-adapter, no-AST, and
zero-work tests. The full repository gate passes with 176 tests and 113 subtests. Independent
publication, contract, and performance audits approve the hardened tree for commit. Generated
client configuration and doctor checks follow.
Status: Candidate frozen. Effective policy, versioned task retrieval, latest-generation diff
receipts, and logarithmic task-context page packing are committed and pushed on `dev`.
Deterministic client configuration and the read-only integration doctor now pass their bounded
publication, path-race, malformed-input, redaction, and no-hidden-work audits. The complete
repository gate passes with 205 tests and 120 subtests. A disposable 1,000-node audit sample passes
the maintained task-context, generation-diff, response-size, counter, and memory gates. Final
clean-revision benchmark evidence and documentation closeout remain before the milestone is marked
complete.
```
Milestones 3–5 remain directional context and are not active.