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
..
.gitkeep	ci: scaffold test and lint workspace	2026-07-22 16:56:25 +00:00
CONSUMERS.md	labels: name what the hourly cron uniquely covers (#199 round)	2026-07-28 19:26:40 +00:00
VENDORED.txt	feat: actions/docs-sync — manifest, script, composite wrapper	2026-07-22 21:38:53 +00:00