2 Commits

Include renames

Author	SHA1	Message	Date
ops-02	c7965e787c	fix(ci): satisfy sanitization + test-enumeration gates for #1129 ... Two gates added to CI after this branch was written: - verify-sanitized: the harness header named the operator repo the live payload was captured from. Genericized; the payload itself was already synthetic. - check-test-enumeration (#1017): the new harness was not on any CI surface. Enumerated in test:framework-shell beside its three ci-queue-wait siblings. All four ci-queue-wait suites green; both gates green locally.	2026-08-19 16:36:28 -05:00
Jason WoltjeandClaude Fable 5	74b3b9e869	fix(git-tools): ci-queue-wait mishandles Gitea statuses:null — push guard hard-fails on any repo without CI ... Gitea's combined-status endpoint returns statuses:null (not []) plus a synthetic aggregate state of "pending" for a commit with zero status contexts (captured live 2026-08-09). The bash parser called that payload malformed -> ASSERTED_NOT_READY exit 3, blocking every push to a CI-less repo; hit twice by velma on two independent clones (shared checkout + fresh sparse clone), proving it environment-independent. - treat statuses:null as empty (both .sh and .ps1) - classify zero contexts as no-status BEFORE consulting the synthetic aggregate state (both twins; honoring it would poll to timeout) - no-status on --purpose push without --require-status is now queue-clear exit 0 (a repo with no CI has no queue), mirroring record_cannot_assert dispositions (push=degraded-pass, merge=hold); merge + --require-status stay fail-closed at exit 3 - red-first regression harness test-ci-queue-wait-no-status.sh (5 cases, incl. the verbatim live Gitea payload and a genuine-pending guard); branch-absent harness still green Co-Authored-By: Claude Fable 5 <[email protected]> Claude-Session: https://claude.ai/code/session_013SAYFkRhQfhguY7AHfiUC8	2026-08-09 03:02:25 -05:00