If composed review publishing is unavailable, the refusal now says whether it was turned off mid-session.
Two distinct refusal messages plus stricter anchor validation in the PR review skill, driven by a runtime switch.
What's wrong with this entry?
When composed review publishing is unavailable, the refusal now distinguishes a feature switched off mid-session from one that was never on.
- Replaces the blanket "re-run /artifact-pr-review and follow the template flow" message with two cases: an operator turning it off during the session (retry later, do not loop) and a session where it was never enabled (start a new session).
- The pr-review skill text now states that a published composed review page is updated only through the acting loop's republish, adds a "Communicating while this skill runs" section, and requires validating a second island
prr-anchorwhosepublishedAtmust matchYYYY-MM-DDTHH:MM:SSZ. - Driven by a runtime switch checked at publish time.
composed review publishing was turned off by an operator during this session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Cloud review: better messages for detached HEAD and wrong base branch
Both mention review code
-
v2.1.223
Cloud review failure message points at plain /code-review
Both mention review code
-
v2.1.239
Code review findings now carry a short summary and a category
Both mention review code