forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
36018be8d1
RM-02's registered fixtures found this before the registry was built. Worse than the banked unknown=>exit 0: ci-queue-wait.sh:266 pipes the payload into a classifier starting 'python3 - <<PY', so python reads its PROGRAM from stdin and json.load never sees the JSON. Proven empirically — success, failure, pending and malformed all classify as unknown, and unknown exits 0. The mandatory pre-push/pre-merge guard therefore returns PASS for every possible input, including a genuinely failing CI. The six observed meaningless greens were not an edge case; they are the only output it can produce. PR #1023 is exactly this fix, open and parked, and its body diagnoses it precisely. Two aggravating details from that body: pr-ci-wait.sh:38 documented the bug and remedy and it was never backported to the mandatory sibling (D-14 propagation with a security-adjacent blast radius); and the fix was opened without re-verification. Escalated for Jason's #1023 disposition. RM-02 records required-vs-actual with DEFECT (owner: RM-03); no RM-03 lane opened, guard not edited. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>