History

clad2 b7775c68ea All checks were successful CI / test (pull_request) Successful in 3m15s 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 6s Details labels / labels (pull_request) Successful in 7s Details docs(changelog): the 0.4.1 -> 0.6.1 gap statement, as a grouped fragment Three Changed entries naming what a reader comparing the two forges' tags would otherwise reconstruct: 0.5.0/0.6.0 arrived by merge and were never released here; the carried ## 0.6.0 section is upstream's record; and the absent 0.6.0 tag is a decision, not an omission. Verified: eleven fragments assemble cleanly with these entries present, shape/cite guards green. Refs #220		2026-08-05 23:10:25 +00:00
..
192.md	fix(forgejo): a read failure names its verb too, and the tests assert the whole diagnostic (#192 )	2026-08-05 13:11:33 +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(198): the action fails closed, the caller decides scheduling, the guard decides the forge (#198 )	2026-08-05 12:30:28 +00:00
199.md	fix(refs-not-closing): gather over REST, so the guard produces verdicts here	2026-08-05 17:11:19 +00:00
200.md	fix(upstream-delta): discovery is git's index, not the filesystem (#200 )	2026-08-05 14:10:56 +00:00
201.md	fix(docs-sync): the mirror is fetched from the forge in play, never a built-in one (#201 )	2026-08-05 11:16:23 +00:00
202.md	docs(runner-probes): restore !207 's release notes; per-run links; honest security lesson	2026-08-05 19:48:04 +00:00
205.md	fix(labels): refuse an unset API root, name transport failures, update the docs	2026-08-05 17:16:30 +00:00
209.md	fix(forge): forge_commit_at — Forgejo serves a single commit at /git/commits/{sha} (#209 )	2026-08-05 15:01:32 +00:00
210.md	test(issueflow): each of the three sites is caught by behaviour, not only by the pin (#210 )	2026-08-05 14:37:37 +00:00
220.md	docs(changelog): the 0.4.1 -> 0.6.1 gap statement, as a grouped fragment	2026-08-05 23:10:25 +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).