{"version":"2.1.221","anchor":"pr-review-payloads-accept-an-in-page-approve-stamp-binding","canonical_anchor":"pr-review-payloads-accept-an-in-page-approve-stamp-binding","heading":"PR review payloads accept an in-page approve stamp binding","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/pr-review-payloads-accept-an-in-page-approve-stamp-binding","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### PR review payloads accept an in-page approve `stamp` binding\n\nReview pages can carry an in-page approve button that gets validated when published.\n\n**What**\n\nThe pr_review payload schema can carry a stamp describing an in-page approve action, checked against the page's identity when the page is published.\n\n**Details**\n\n- `stamp` is optional and holds a tool name, an input record capped at 8 keys, and a statePath.\n- Validation runs at publish time against the page identity, and failure messages name the fix explicitly.\n- Capabilities-manifest validation now runs in two shapes depending on whether the publish is a republish.\n- Behind `tengu_walnut_sconce`, fallback false.\n\n**Evidence**\n\n`stamp.input has too many keys (max 8)`\n\n- Flag `tengu_walnut_sconce`: Not enough to say (read for one account on one subscription tier against v2.1.221; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Names: `tengu_walnut_sconce`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}