claude-bot-andresmgsl 8cf3c335df labels: name what the hourly cron uniquely covers (#199 round) ... The trigger comments, CONSUMERS stub, changelog, and reusable labels.yml comment said "events carry every real state change in seconds; the cron only backstops a forgotten handoff." That is backwards: no subscribed event wakes this sweep for a review verdict landing (no pull_request_review trigger), blocker:ci-red set/cleared, blocker:conflict when another PR merges, or the time-based stale/48h-reclaim. The hourly cron is the sole discovery path for those four classes, not a forgotten-handoff net — so the comments now name them and warn against deleting the cron (AC5). codex-2 / kimi-2 (both blocking, round 2 @0a812c4b).		2026-07-28 19:26:40 +00:00
..
ci.yml	feat: reconciler warns on a release-shaped PR missing its release label	2026-07-24 11:54:49 +00:00
labels.yml	labels: name what the hourly cron uniquely covers (#199 round)	2026-07-28 19:26:40 +00:00
release-exercise.yml	test: exercise release fixtures fragment-shaped; record the #115/#116 trio interaction	2026-07-24 11:11:23 +00:00
release.yml	release: prepare 0.3.0	2026-07-24 17:06:25 +00:00
self-labels.yml	labels: name what the hourly cron uniquely covers (#199 round)	2026-07-28 19:26:40 +00:00
self-release.yml	feat: dogfood bootstrap — ceremony adopts its own ceremony (#11)	2026-07-22 22:19:50 +00:00