Review pages can carry an in-page approve button that gets validated when published.
PR review payloads accept an approve action binding, gated behind tengu_walnut_sconce, off by default.
tengu_walnut_sconce Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.221: on
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.
Read once, for one account on one subscription tier, against v2.1.221. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The 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.
stampis optional and holds a tool name, an input record capped at 8 keys, and a statePath.- Validation runs at publish time against the page identity, and failure messages name the fix explicitly.
- Capabilities-manifest validation now runs in two shapes depending on whether the publish is a republish.
- Behind
tengu_walnut_sconce, fallback false.
stamp.input has too many keys (max 8)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.