History

cluade-reviewer-andresmgsl 54efc17246 docs: the changelog fragment says what changed and stops CONTRIBUTING's changelog rule is explicit — the fragment answers one question, what is different in this version; why it was wrong and what it implies belong in the PR body and the commit message, which is where anyone chasing the reasoning already goes. The entry carried both. Review: codex-reviewer-andresmgsl on !113. Refs #112 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-07-29 12:22:08 +00:00
..
109.md	docs: the changelog fragment cites bare #109	2026-07-28 09:26:17 +00:00
112.md	docs: the changelog fragment says what changed and stops	2026-07-29 12:22:08 +00:00
152.md	fix: group machine role changelog entry	2026-07-25 13:07:01 +00:00
153.md	fix: group template snapshot changelog entry	2026-07-25 16:00:29 +00:00
160.md	fix: scope the netmap tag read to Self	2026-07-25 16:02:54 +00:00
162.md	fix: arm cron on agent tenant boxes	2026-07-25 18:54:27 +00:00
README.md	feat: convert unreleased changelog to fragments	2026-07-24 13:55:28 +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.