1.9 KiB
1.9 KiB
Doc Review: fix-context-sizing
Status: PASS
Docs Updated
config.md— added## Loop Role Modelssection between System Requirements and Framework Version.prompts/decompose.md— added**4k VRAM**row in peak-context Guideline and(4k VRAM)rows in Sub-Task Size Targets; added≤ 16k VRAM: REFUSEline as a non-negotiable floor.tasks/fix-context-sizing/SPEC.mdSPEC.md, IMPLEMENTATION.md — present in task folder.tests/test_context_sizing.py— 15 new test cases.
Documentation Gaps Closed
- Loop role contract now exists in user-facing
config.md(was previously implicit / absent). decompose.md's context budget guidance now exposes the 4k tier and refuses ≤16k budgets explicitly, so users decomposing tasks for small models can plan correctly.--loop-modeCLI flag is documented in script's--helpoutput.- JSON output schema now carries
available_context_kbandloop_mode_eligiblewhich downstream consumers (loop runner) can rely on.
Gaps Remaining (out of scope — deferred to Tier 2 per D17)
README.mddoes not yet document--loop-modein the human-facing CLI section (Tier 2 task).- Dashboard does not surface
loop_mode_eligible(v1.1 panel). prompts/decompose.mdline 135 still says "If model detection fails, use 128k tokens as default" — the auto-detection flow's fallback. This is the user-facing decompose prompt's narrative; changing it would alter how decomposition agents behave in the research phase. Left intact; loop runner uses--loop-modeinstead which refuses on this condition.
Cross-References
- DESIGN.md not produced — task went directly research → implement per locked plan (Tier 1 fixes don't warrant a separate design phase).
- This DOC_REVIEW covers the doc-side of the task; referee step is final.
Verdict
Documentation is consistent with SPEC. No blocking gaps.