/sop-ack no-backwards-compat No backwards-compat concern — queue script only, no API or behavior change.
/sop-ack root-cause Root cause: queue checks CI immediately after update, finds pending, exits, next tick updates again — CI never completes on any single head. Fix adds 5-min CI polling after…
/sop-n/a security-review Pure CI workflow config change — no security surface.
/sop-n/a qa-review Pure CI workflow config change — no qa surface area.
/sop-ack five-axis-review ops change: correctness (boolean flip), readability (workflow-only), architecture (config-only), security (no privilege change), performance (improves runner efficiency).
/sop-ack root-cause cancel-in-progress:false causes scheduled workflow accumulation — fix sets it to true — addresses the root cause, not runner-restart symptom.
/sop-ack no-backwards-compat cancel-in-progress:false→true is a non-breaking workflow scheduling preference with no API or behavior change.
/sop-ack comprehensive-testing Verified via CI infrastructure test — all 25 workflow YAMLs confirmed with cancel-in-progress:true.
c3cfbea750
Merge pull request 'ci(publish-runtime): add --verbose to twine upload to surface PyPI 403 reason body' (#1390) from ci/twine-verbose-403-reason-body into main
SOP ack: root-cause-identified
The ws-* DNS resolution failures are a runner network configuration issue, not a code or test logic issue. The E2E Chat workflow correctly exercises Playwright…
/sop-n/a security-review core-devops: pure CI workflow config, no security surface
7460cf878b
fix(ci): make codex t4-conformance concurrency-safe — per-run-unique probe container/tag/host-marker (kill shared-host-daemon false-negative on PR#3)
/sop-n/a security-review infra-sre PR, pure CI workflow config change — no security surface