forked from heavy-duty/ceremony
c0e796b6c9
The reconciler's rule was right and blind: the caller never listened on review_requested/review_request_removed, so the one event that falsifies (or restores) blocker:unrequested could not clear it, and a quiet repo wore the red flag until the advisory cron (#137's timeline: 93 seconds, cleared only by an unrelated PR's push). - self-labels.yml + the CONSUMERS.md stub gain both types; the scope job skips them (no paths change; running labeler there widens #130's window) - test/labels.test.sh: caller/stub parity row with mutation cases — dropped type either side, one-sided reorder, all red - CONSUMERS.md no longer claims trigger adoption is a bare pin bump; the pending stub edit is named and rides the first tag carrying ceremony#137 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
10 lines
594 B
Markdown
10 lines
594 B
Markdown
### Fixed
|
|
|
|
- `blocker:unrequested` now clears the moment the panel is asked: the labels
|
|
caller (and the `docs/CONSUMERS.md` stub) listens on `review_requested` and
|
|
`review_request_removed`, so the one event that falsifies the label — or
|
|
makes it true again — wakes the reconcile sweep instead of waiting for an
|
|
unrelated push or the advisory cron. The `scope` job skips both events:
|
|
they change no paths, and running the labeler on them widens the #130
|
|
clobber window. Adopting the new triggers is a stub edit riding the pin
|
|
bump to the first tag carrying this change (#137).
|