History

cluade-reviewer-andresmgsl 7d52b2cd4a feat(forge): refuse loudly when the client cannot speak the forge The preflight half of #188, landed first so it stands alone: the forge is decided once, before any sweep, and a client that cannot speak it exits non-zero with a named reason. Measured against forgejo.heavyduty.builders at `84bb1a4` — two of the three actions reported SUCCESS having read nothing: labels-scope exit 0 "no .github/labeler.yml" (the file is HTTP 200) labels-reconcile exit 0 "reconciled." (zero PRs enumerated) issueflow-reconcile exit 1 "unexpected end of JSON input" labels-reconcile's blind-sweep warning (#96) could not fire: it counts unreadable PRs against a list `gh pr list` never produced, and a process substitution's failure does not trip set -e, so total stayed 0. Installing gh makes it worse, silencing the one loud failure. Detection is measured, not inferred from docs: a real forgejo-runner v6.3.1 job (probe task 278) shows Forgejo populating the whole GITHUB_* namespace, so GITHUB_ACTIONS proves nothing. GITHUB_API_URL's shape, GITEA_ACTIONS and GITHUB_SERVER_URL do. The same probe shows the runner image carries neither gh nor stoke, which is what makes the forgejo backend REST. Tests declare CEREMONY_FORGE at the forge boundary rather than stubbing gh and staying silent about the forge — the boundary move term 5 asks for. Refs #188		2026-08-02 18:29:08 +00:00
..
188.md	feat(forge): refuse loudly when the client cannot speak the forge	2026-08-02 18:29:08 +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).