mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-02 17:40:02 +02:00
garrytan
5d032ef299
- A1: the retired Eng lexical oracle (evaluateEngSeedCoverage, isEngSeedDecisionAUQ), the completion-handoff detector and the retained corpus had no paid caller since v1.87.6; delete their 26 replay files, ~2.6k helper LOC and fixtures, and the dead blocks in 8 mixed files (live hasNativePlanTerminal / batching assertions stay). - A2: dead viewport approvers in autoplan-artifact-permission and their 11 replay files + fixtures; recorder/launcher cases stay. - A3: never-wired oracles and seeders (autoplan-phase-order, eng-finding-fixture, ceo-paired-fixture, design-ui-scope, plan-skill-completion, pty-current-screen, required-reads, transcript-section-logger); plan-seed-submission now decodes through the production createPtyScreen; section manifests name their actual guard. - A4: zero-reference helper exports, plus execGit and invokeAndObserve found by the reachability pass. - 52 fixtures orphaned by the deletions; touchfile and selection-table entries for every deleted path.
27 lines
1.4 KiB
JSON
27 lines
1.4 KiB
JSON
{
|
|
"$schema": "https://gstack.dev/schemas/section-manifest.json",
|
|
"skill": "review",
|
|
"version": 1,
|
|
"note": "PASSIVE registry (v2 plan T9 / CM2). Fields are IDs, file paths, human titles, and human-readable trigger text ONLY. The skeleton's decision-tree prose is the ONLY place that decides WHEN to read a section; required section reads are checked by test/carve-section-loading-review.test.ts. No machine predicate here — see docs/designs/v2_PLAN.md:663.",
|
|
"sections": [
|
|
{
|
|
"id": "plan-completion",
|
|
"file": "plan-completion.md",
|
|
"title": "Plan completion audit (deep pass of scope drift)",
|
|
"trigger": "auditing plan completion — plan file discovery, item extraction, verification-mode classification, and cross-reference against the diff (the deep pass that follows Step 1.5's scope-drift check)"
|
|
},
|
|
{
|
|
"id": "review-army",
|
|
"file": "review-army.md",
|
|
"title": "Review Army — specialist dispatch and findings merge",
|
|
"trigger": "dispatching the Review Army specialists and merging their findings after the critical pass (Step 4.5)"
|
|
},
|
|
{
|
|
"id": "adversarial",
|
|
"file": "adversarial.md",
|
|
"title": "Adversarial review (always-on)",
|
|
"trigger": "running the always-on adversarial review — Claude subagent plus Codex passes — after the staleness checks and before persisting the Eng Review result (Step 5.7)"
|
|
}
|
|
]
|
|
}
|