{"version":"2.1.221","anchor":"republishing-a-pr-review-page-from-an-older-cli-is-refused","canonical_anchor":"republishing-a-pr-review-page-from-an-older-cli-is-refused","heading":"Republishing a PR review page from an older CLI is refused","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/republishing-a-pr-review-page-from-an-older-cli-is-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Republishing a PR review page from an older CLI is refused\n\nRepublishing a PR review page made by an older CLI is refused, so you re-run the skill instead.\n\n**What**\n\nThe republish path detects pages published by a CLI that predates the current approve control and stops rather than overwriting them.\n\n**Details**\n\n- The guard requires all three conditions together: no `prr-stamp` island in the stored page, no script matching the pinned approve-script hash, and the template's `stamp-control` markup block missing from the page.\n- 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.\n- Reachable only through the artifact-pr-review acting\/republish loop.\n\n**Evidence**\n\n`the page predates the approve control this CLI requires`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}