feat(pre-push-safety-net): record admission vetoes and meet M1a on NodeGoat

Add group 9 to the approved task plan as the bounded owner amendment release
milestone M1a requires, implement the task-local recorded-veto evaluation flag,
and run the three pinned NodeGoat revisions under it.

The flag re-runs the production comparison and admission over a lifted copy of
the same evidence and records each veto instead of applying it. Recognized
completeness vetoes are lifted and logged; failures never are, because silence
from a failure is not a quiet fixed twin. It is off by default, accepted only on
explicit base/head replay, refused in Git stdin mode, labels every payload it
produces, and admits no defect even when a lifted candidate otherwise would.

M1a outcome, inside its one-week box and with expectations frozen on disk first:
the three entailed <lambda>2 witnesses are present at contributions.js 32-34; the
fixed twin was genuinely analyzed and quiet, answering its target question with
zero rows and no deadline reason while the same findings appear as base-only; the
unchanged revision was analyzed and recorded unchanged. The kill criterion did
not trigger.

Five vetoes fired and were recorded. M1a also corrected the diagnosis: with all
five lifted the detection still stops at operation_correspondence_unresolved,
because a newly introduced operation sits on a changed line and has no base
anchor. The unchanged revision resolves its base location on the same lines and
classifies as unchanged, which isolates correspondence as the mechanism. That
fifth veto was not in the earlier four-veto diagnosis and is now M1b's central
repair.

Diagnosis only. No defect admitted, no capability enabled, no gate changed, no
latency claim; the 900-second development budget cannot measure the hook gate.
Rollout and task 8.3 remain NO-GO.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01EmM1j46qgKMh3zqD1QMwEo

.kiro/steering/safety-net.md

@@ -6,9 +6,11 @@ WordPress-first release framing in older steering; historical measurements remai
 Release order accepted 2026-09-14: first prove one useful Node changed-code comparison
 with an analyzed quiet fixed twin, then make the same analysis fast, verify PHP/Python
 transfer, qualify independently, and enable only passing advisory capabilities. See
-[the milestone spec](../specs/pre-push-safety-net/release-milestones.md). We are at M1a
-(show the detection with vetoes recorded, one-week box), then M1b (repair only what fired);
-task counts and an experimental alpha tag do not establish release readiness. PMPro
+[the milestone spec](../specs/pre-push-safety-net/release-milestones.md). M1a is met
+(2026-09-16: witness shown, fixed twin analyzed and quiet, five vetoes recorded); we are at
+M1b, repairing only what fired. M1a added a fifth veto the earlier diagnosis missed:
+operation correspondence for an operation on a changed line.
+Task counts and an experimental alpha tag do not establish release readiness. PMPro
 remains a core regression/development case; any PMPro core retune still requires frozen
 Node transfer evidence. This sequence supersedes older runtime-first next-step wording.