ceremony/changelog.d/284.md

### Fixed

- Claiming a `needs-ruling` issue no longer buys its escalation another 7
  quiet days: the issue-side ruling clock reads comments alone — an
  assignment is the claim clock's fact — and LABELS.md now names what each
  surface's clock reads (#284).
fix: the issue-side ruling clock reads comments only (#284) Claiming a needs-ruling issue dated it through the assigned timeline event, silencing the 7-day escalation nudge at exactly the moment a builder started working through it. The ruling block now reads last_issue_comment_activity (D1); the reclaim clock keeps the assignment (D2) because there the assignment IS the claim; post-merge hands its evidence read to the ruling block instead of reading again (D6, D7); the claimed branch reads both clocks at its top, before anything it posts. LABELS.md and lib/ruling.sh now say what each surface's clock reads (D4, D5). The #257-era order compositions move to the comments read — the timeline is no longer an input the issue clocks take, and its unreadability no longer holds unrelated writes hostage; that narrowing is pinned rather than implied. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> 2026-08-04 16:16:19 +00:00			`### Fixed`

			- Claiming a `needs-ruling` issue no longer buys its escalation another 7
			`quiet days: the issue-side ruling clock reads comments alone — an`
			`assignment is the claim clock's fact — and LABELS.md now names what each`
			`surface's clock reads (#284).`