revert(gate): restore ADR 0039 to proposed — acceptance is the decision-maker's call #549
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!549
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "gate/adr-0039-restore-proposed"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Reverting the proposed -> accepted flip on ADR 0039 that I made without the
decision-maker's confirmation, and reopening tracker #546 (closed prematurely
by the earlier merge).
State restored to the process-correct configuration the gate enforces:
record 0039 = proposed, tracking issue #546 = open. adr check (with the
remote issue leg) passes: "OK: 39 records, 1 proposed records checked".
Also of record, investigated per review: the remote adr-check leg is already
in gate.sh's fast phase (lines 210-212 — --fast only excludes the heavy
analyzer block). Why it appeared otherwise in this work: the last pre-merge
fast run passed while #546 was still open, and no fast run happened between
the #547 merge (which closed the issue) and the first full-gate run. The
timelines, not the partitioning, hid the C11 violation from --fast.