History

codex-bot-andresmgsl 79e747b163 Some checks failed CI / action-exercise (pull_request) Successful in 29s Details CI / self-guards (pull_request) Failing after 32s Details CI / release-exercise (pull_request) Successful in 39s Details CI / docs-sync-exercise (pull_request) Successful in 12s Details labels / labels (pull_request) Successful in 14s Details Refs guard / refs-not-closing (pull_request) Successful in 11s Details CI / test (pull_request) Failing after 1m11s Details docs: describe merge-door resume recovery		2026-08-31 11:21:09 +00:00
..
269.md	docs: correct upstream sync campaign record	2026-08-27 10:19:53 +00:00
271.md	docs: describe atomic release publication	2026-08-30 09:27:56 +00:00
273.md	docs: describe merge-door resume recovery	2026-08-31 11:21:09 +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).