History

codex-bot-andresmgsl 9f07c91faf Some checks failed labels / labels (pull_request) Failing after 18s Details CI / test (pull_request) Has been cancelled Details CI / release-exercise (pull_request) Has been cancelled Details CI / self-guards (pull_request) Has been cancelled Details CI / action-exercise (pull_request) Has been cancelled Details CI / docs-sync-exercise (pull_request) Has been cancelled Details Refs guard / refs-not-closing (pull_request) Has been cancelled Details docs: group the 229 changelog fragment		2026-08-20 01:36:32 +00:00
..
217.md	docs: record delivered 0.6.1 runner exercise	2026-08-09 20:35:49 +00:00
229.md	docs: group the 229 changelog fragment	2026-08-20 01:36:32 +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).