mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-03 01:46:55 +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.2 KiB
JSON
27 lines
1.2 KiB
JSON
{
|
|
"$schema": "https://gstack.dev/schemas/section-manifest.json",
|
|
"skill": "land-and-deploy",
|
|
"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-land-and-deploy.test.ts. No machine predicate here — see docs/designs/v2_PLAN.md:663.",
|
|
"sections": [
|
|
{
|
|
"id": "first-run-validation",
|
|
"file": "first-run-validation.md",
|
|
"title": "First-run dry-run validation (teacher mode)",
|
|
"trigger": "running the first-run dry-run validation — Step 1.5's check returned FIRST_RUN or CONFIG_CHANGED (skip on CONFIRMED)"
|
|
},
|
|
{
|
|
"id": "readiness-gate",
|
|
"file": "readiness-gate.md",
|
|
"title": "Pre-merge readiness gate",
|
|
"trigger": "the pre-merge readiness gate (Step 3.5) — the last check before the irreversible merge"
|
|
},
|
|
{
|
|
"id": "merge-and-deploy",
|
|
"file": "merge-and-deploy.md",
|
|
"title": "Merge the PR + deploy strategy detection",
|
|
"trigger": "merging the PR and detecting the deploy strategy (Steps 4-5)"
|
|
}
|
|
]
|
|
}
|