heavy-duty/ceremony
7
0
Fork 2
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions
ceremony/CHANGELOG.md

32 lines
2.9 KiB
Markdown
Raw Normal View History

feat: dogfood bootstrap — ceremony adopts its own ceremony (#11) VERSION at 0.1.0-dev, the armed CHANGELOG.md, drills/README.md (what a drill means here), the self-callers (self-release.yml, self-labels.yml — local uses:, the one form consumers must never copy), .github/labeler.yml for the scope job, and the three self-guards in CI. labels.yml gains the self-consumption bypass (release.yml's twin) so the label bootstrap can run before any release tag exists; action-exercise's armed/drill-recorded scratch steps move to self-guards per their own eviction note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 22:19:50 +00:00
# Changelog
The curated history of the ceremony itself. Each release's section is
published verbatim as that release's body (lib/changelog.sh extracts it),
so entries say what changed, cite the issue, and stop.
## Unreleased
fix: guard cross-repo issue references
2026-07-23 11:38:14 +00:00
- `issueflow-reconcile` — keep cross-repo references out of local dependency decisions and require triage to resolve cross-repo blockers by hand (#61).
docs: needs-ruling doctrine — LABELS row + D5–D9 rationale, escalation mechanics in TRIAGE/BUILDER/REVIEWER, changelog (#51) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 00:49:21 +00:00
- `needs-ruling` — the cross-cutting flag for a pending human decision, excluded from `state:needs-human` and from the staleness sweep (#51).
docs: define cross-repo discovery guards
2026-07-23 11:21:52 +00:00
- Cross-repo doctrine: the panel is the PR's repo's roster, a review request is authorization but not panel membership, and `Part of <repo>#N` replaces the `Closes #N` that cannot cross repos (#57).
feat(guards): wire runner-isolated — self-guards step, consumer entry, changelog (#58)
2026-07-23 11:18:56 +00:00
- `actions/runner-isolated` — a `pull_request`-triggered job may never run on a self-hosted runner (#58).
docs(labels): the ruling sweep behaviors in LABELS.md, CONSUMERS.md, CHANGELOG LABELS.md's needs-ruling paragraph gains the bare-flag check and the markerless 7-day nudge; CONSUMERS.md names them in the labels job and states the caller stub is unchanged since #18 (a pin bump is the whole upgrade); one CHANGELOG line under Unreleased (#52). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 11:59:05 +00:00
- The sweep's `needs-ruling` invariants, one implementation for both surfaces: the issue-side staleness exemption, the bare-flag check (comment-only, the label is never removed), and the 7-day nudge to the decider (#52).
feat: exempt offsite claims from reclaim clock
2026-07-23 12:48:04 +00:00
- `offsite` — protect claimed issues whose PR lives in another repository from the claim-reclaim clock (#68).
feat: nudge resolved offsite claims
2026-07-23 13:17:39 +00:00
- `issueflow-reconcile` — nudge once when an `offsite` flag outlives every visible cross-referenced PR (#69).
docs: define the ruling escalation contract
2026-07-23 14:57:51 +00:00
- Ruling doctrine — define every human-owned trigger, the fixed escalation shape, and the 0–24h builder-to-triage ladder (#72).
feat: observe the escalation shape and the ladder's rungs lib/ruling.sh gains the mechanical half of #50 D12-D15: the comment body rides the fetch as base64 (rows stay line-oriented), ruling_shape_decision checks the four line-anchored bold-tolerant field labels, ruling_deadline_decision derives the rung from the labeled epoch, ruling_default_decision parses the Default: line for wording only, and reconcile_ruling wires them with bare-stops-here exclusion — every write a comment, one per marker per episode, both surfaces via the shared lib. Part of #73. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 15:43:01 +00:00
- The sweep observes the escalation contract: a malformed escalation is named field-by-field, and the ladder's 12h/24h rungs each draw one comment to the flag-setter — comment-only, per-episode, both surfaces (#73).
docs: the operator notifier's needs-ruling queue and triage's past-24h wake FLEET.md's wake conditions gain #50 D16: notify.sh's second query (open issues and PRs labelled needs-ruling), one tracked message per item edited in place across the ladder's four rungs and removed on clearance, the message's contents, triage's past-24h pickup, and the on-paper caveat. Nothing box-side sets, clears or decides the flag. Part of #50. Closes #74. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 16:16:16 +00:00
- FLEET.md — the operator notifier's `needs-ruling` queue (one tracked message per item, edited in place across the rungs) and triage's past-24h wake condition; a spec on paper until an operator updates the box (#74).
docs: the parked claim and the one-build-at-a-time rule The one-issue-at-a-time bullet counted claims when it meant build work in flight; the 2026-07-23 board (#15, #16 parked beside #73) proved the count wrong. BUILDER.md now defines the three parked shapes, the declared-never-inferred park comment, and unparking; TRIAGE.md names a directed hold as a park (#77). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 16:26:13 +00:00
- One issue at a time counts build work in flight: the parked claim's three shapes, its declared-never-inferred comment, and triage's duty to name a directed hold as a park (#77).
docs: needs-ruling doctrine — LABELS row + D5–D9 rationale, escalation mechanics in TRIAGE/BUILDER/REVIEWER, changelog (#51) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 00:49:21 +00:00
release: 0.1.0 The ceremony PR — two edits, per the amended #11: VERSION 0.1.0-dev -> 0.1.0, and the changelog stamp with the re-arm in the same edit (## Unreleased -> ## 0.1.0 — 2026-07-22, an empty ## Unreleased put back on top — box#108). No third stamp: both CEREMONY_SELF_REF carriers already read "0.1.0", and self-ref-check's bare-tree rule wants exactly that. drills/0.1.0.md follows once the rehearsal runs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 23:27:56 +00:00
## 0.1.0 — 2026-07-22
feat: dogfood bootstrap — ceremony adopts its own ceremony (#11) VERSION at 0.1.0-dev, the armed CHANGELOG.md, drills/README.md (what a drill means here), the self-callers (self-release.yml, self-labels.yml — local uses:, the one form consumers must never copy), .github/labeler.yml for the scope job, and the three self-guards in CI. labels.yml gains the self-consumption bypass (release.yml's twin) so the label bootstrap can run before any release tag exists; action-exercise's armed/drill-recorded scratch steps move to self-guards per their own eviction note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 22:19:50 +00:00
- `lib/version.sh` — one version abstraction, `file` and `package-json` backends (#3).
- `lib/changelog.sh` + `bin/changelog-section` — the one canonical changelog-section extractor (#4).
- `actions/changelog-armed` — the version-keyed arming guard (#5).
- `actions/changelog-monotonic` — shipped release headings are append-only: no deletion, no duplication (#6).
- `actions/drill-recorded` — a release tree must carry its drill record (#7).
- `lib/decide.sh` — the merge door's five-state decision, pure and exhaustively tested (#8).
- `.github/workflows/release.yml` + `lib/facts.sh` — the reusable two-door release workflow (#9).
- `.github/workflows/labels.yml` + `actions/labels-reconcile` — label taxonomy bootstrap and PR-state reconciliation (#10).
- Ceremony adopts its own ceremony: `VERSION`, this changelog, the drill doctrine, the self-callers, and the self-guards in CI (#11).
Reference in a new issue Copy permalink