History

cluade-reviewer-andresmgsl 728102a3ba All checks were successful CI / test (pull_request) Successful in 3m3s Details CI / release-exercise (pull_request) Successful in 11s Details CI / self-guards (pull_request) Successful in 6s Details CI / action-exercise (pull_request) Successful in 6s Details CI / docs-sync-exercise (pull_request) Successful in 6s Details Refs guard / refs-not-closing (pull_request) Successful in 5s Details labels / labels (pull_request) Successful in 45s Details fix(issueflow): issue_payload_valid refuses an empty payload on jq 1.6 too (#198 ) `CI / test` was red at `97e63ac` on a case that passes on this box: upstream's own "an empty payload is refused". The cause is not the test. `jq -e` disagrees with itself across versions on EMPTY input. jq 1.7 exits 4 — no valid result was ever produced. jq 1.6 exits 0. Measured both ways today against the same filter. This instance's runner image (ghcr.io/catthehacker/ubuntu:act-22.04) carries jq 1.6. So on this forge the guard #247 D3 added specifically to refuse an unreadable read was ACCEPTING one: an empty body read as a valid issue payload, and the sweep would have reconciled an issue from a payload it never received. The test is upstream's, it is correct, and it passes on a GitHub runner — which is why upstream never saw this. The fix does not depend on jq's exit code for an input it never receives: the payload is read, emptiness is decided in the shell, and jq judges only a non-empty body. Verified under BOTH jq versions, not just the one on this box: empty refused and healthy accepted on 1.6 and 1.7, and the whole suite green under jq 1.6 — 28 test files, 0 failed — as well as under 1.7. Refs #198		2026-08-05 12:22:20 +00:00
..
195.md	fix(labels): panel and triage name identities that exist on this forge (#195 )	2026-08-04 19:09:16 +00:00
198.md	fix(issueflow): issue_payload_valid refuses an empty payload on jq 1.6 too (#198 )	2026-08-05 12:22:20 +00:00
README.md	feat: ceremony flips to grouped — changelog.d/shape = grouped, five fragments converted, docs per D6	2026-07-25 13:14:05 +00:00
shape	feat: ceremony flips to grouped — changelog.d/shape = grouped, five fragments converted, docs per D6	2026-07-25 13:14:05 +00:00

README.md

changelog.d/ — the next release's section, one fragment per issue

Machine-assembled by bin/changelog-assemble (#112): every PR that changes behavior writes one file here — <issue>.md, the exact prose that will be published, nothing else — and the release PR folds them all into the next ## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct filenames never conflict, which is this directory's whole reason to exist. This README is the marker that keeps the directory tracked when it holds no fragments (#112 D1) — changelog-armed refuses a tree without it; do not delete it. The shape sentinel beside it declares the set's shape — grouped here, so every fragment carries ### headings (#182).