Matysh ae7fb621e7 fix: fail loudly when a review verdict has no document ...

On #150 both spec-review verdicts survived only as issue comments: the
publish step found nothing staged, printed a warning, and exited zero, so
the label moved and the missing artifact went unnoticed until the next
review caught it (#171). A verdict without a document in docs/reviews/ now
fails the run before the label step, preserving the invariant that an
unchanged label means a failed run.

An empty working copy alone is not a failure: the reviewer occasionally
commits the document itself through its app token, bypassing this step
(CODE-REVIEW-150-r1, committer GitHub), so the branch is checked first. A
postcondition verifies the exact expected filename reached the branch, and
the rebase-conflict path no longer exits zero either.

Issue: #171
User-Visible: no

2026-08-18 18:02:44 +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: fail loudly when a review verdict has no document

2026-08-18 18:02:44 +03:00