History

cluade-reviewer-andresmgsl 9a229ee643 release: stamp 0.4.1 The three stamps, in one commit as the ceremony requires: VERSION goes bare, the self-ref pin follows it, and the changelog section is the assembler's output rather than a hand edit. 0.4.1 is the forge release. Everything in the section comes from #188's single fragment: ceremony stops being gh-only. `lib/forge.sh` selects a backend from the runner's own environment, `lib/forge-github.sh` and `lib/forge-forgejo.sh` implement one call surface twice, and the reconcilers preflight before they sweep — so a GitHub-shaped client pointed at a Forgejo instance is a named refusal instead of a sweep that reads nothing and reports success. Verified on this instance before stamping: the first post-merge `labels` run on main (`7fc9afe`, task 467) came back SUCCESS — the reconciler's first green run on Forgejo, and the evidence the section's claims are not merely asserted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-04 10:01:21 +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

cluade-reviewer-andresmgsl 9a229ee643 release: stamp 0.4.1

The three stamps, in one commit as the ceremony requires: VERSION goes
bare, the self-ref pin follows it, and the changelog section is the
assembler's output rather than a hand edit.

0.4.1 is the forge release. Everything in the section comes from #188's
single fragment: ceremony stops being gh-only. `lib/forge.sh` selects a
backend from the runner's own environment, `lib/forge-github.sh` and
`lib/forge-forgejo.sh` implement one call surface twice, and the
reconcilers preflight before they sweep — so a GitHub-shaped client
pointed at a Forgejo instance is a named refusal instead of a sweep that
reads nothing and reports success.

Verified on this instance before stamping: the first post-merge `labels`
run on main (7fc9afe, task 467) came back SUCCESS — the reconciler's
first green run on Forgejo, and the evidence the section's claims are
not merely asserted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-04 10:01:21 +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).