831fe239d9
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>
29 lines
2.5 KiB
Markdown
29 lines
2.5 KiB
Markdown
# 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
|
||
|
||
- `issueflow-reconcile` — keep cross-repo references out of local dependency decisions and require triage to resolve cross-repo blockers by hand (#61).
|
||
- `needs-ruling` — the cross-cutting flag for a pending human decision, excluded from `state:needs-human` and from the staleness sweep (#51).
|
||
- 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).
|
||
- `actions/runner-isolated` — a `pull_request`-triggered job may never run on a self-hosted runner (#58).
|
||
- 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).
|
||
- `offsite` — protect claimed issues whose PR lives in another repository from the claim-reclaim clock (#68).
|
||
- `issueflow-reconcile` — nudge once when an `offsite` flag outlives every visible cross-referenced PR (#69).
|
||
- Ruling doctrine — define every human-owned trigger, the fixed escalation shape, and the 0–24h builder-to-triage ladder (#72).
|
||
- 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).
|
||
|
||
## 0.1.0 — 2026-07-22
|
||
|
||
- `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).
|