Treat gate-driven collateral CRITICALs as in-scope for the same diff t…
Decision
Treat gate-driven collateral CRITICALs as in-scope for the same diff that triggered them, not as separate tickets. Confirmed pattern from this session: my upload-conversion change forced fixes to delete-guard, network-bypass, biome-excludes, healthcheck-auth — all real bugs in adjacent code, all minimal-LoC fixes, none requiring architectural rework.
Rationale
Anti-pattern would be: override the gate, ship narrow scope, file 4 follow-up tickets that decay in a backlog. Gate forces “while-touching” fixes which the codebase needs anyway. The cost of fixing-in-flight is < cost of ticket-context-reload later. Validated empirically: 4 fixes added ~80 LoC and 2 build cycles; smoke still passed; deploy went green on third gate attempt.
Alternatives Rejected
Outcome
Pending