Matysh 4e539b02df fix: the guard says why it refused, in the issue ...

A review label promises work. When the guard declined it wrote the reason to the
run log and nothing else, so the issue sat in a status nobody was acting on and
nobody could tell. #123 showed it: an outside reporter's issue was walked up to
S4-spec-review, the guard refused in nine seconds because only the owner's issues
enter the process, and the issue itself said not a word.

Refusals that a human can act on now become a comment: wrong author, blocked,
review-4. Only when a stage was actually recognised, so an unrelated label change
stays silent.

This is the same defect as the merge conflict that left the label untouched, seen
from the other side. The pattern is worth naming: doing nothing quietly is the
most expensive thing a pipeline can do.

Issue: #114
User-Visible: no

2026-08-13 20:36:25 +03:00

..

ISSUE_TEMPLATE

docs v1.44.1: add the Telegram community chat (@ha_houseplan)

2026-07-27 12:51:48 +03:00

workflows

fix: the guard says why it refused, in the issue

2026-08-13 20:36:25 +03:00