Republishing a PR review page made by an older CLI is refused, so you re-run the skill instead.
A republish guard for older PR review pages sits inside the gated artifact PR review flow.
What's wrong with this entry?
The republish path detects pages published by a CLI that predates the current approve control and stops rather than overwriting them.
- The guard requires all three conditions together: no
prr-stampisland in the stored page, no script matching the pinned approve-script hash, and the template'sstamp-controlmarkup block missing from the page. - On a match it refuses the republish, tells the user to re-run the skill for a fresh page, and notes that decisions already recorded on the old page stay visible there.
- Reachable only through the artifact-pr-review acting/republish loop.
the page predates the approve control this CLI requires
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.