Repository navigation
Lever 2: one local entry point that runs the SAME guard scripts CI runs (no second copy, F1 #2640) — catch guard reds before push #4416
Description
Problem
16 of the 23 failing jobs on RC PR #4318 were guard reds that could run on a laptop, and each one cost a ~35–50 min CI cycle to discover (baseline: ~/Desktop/rc-speed-report.md). There is no single local command that runs the same guard scripts CI runs. A second hand-maintained copy would drift, as the two dogfood runners did (F1, #2640: 86 lines of drift).
Fix
One entry point (e.g. scripts/ci_guards.sh [--tree|--cargo|--all]) that reads the SAME manifest the CI guard jobs execute (lever 0, #4415), with no second list. make guards and a pre-push hook call it. CI calls it too, so local green means the same thing as CI green for the cargo-free and cargo guards.
Falsification
- Add a guard row to the manifest. It runs both locally and in CI, with no second edit.
- A drift check fails if ci.yml invokes a guard script that is not in the manifest.
- Plant a violation. The local entry point goes red, reporting the same step name CI would.
Activity
ci(guards): every guard step runs and every failure is reported — one…
noahgift commentedon Oct 14, 2026
P0 to P1 (2026-10-14 P0 triage): P0 now means it blocks the next release or carries the operator's own words on it; this issue does neither, so it stays on the 0.71.0 milestone at P1.
noahgift commentedon Oct 14, 2026
Folded into #3676 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch:
fb/4416-lever2,PMAT-4416-guards-local-wip.Agent: aprender-clerk