Approvable, stampable PR-review artifact pages are built in but completely unreachable in this build.
A /artifact-pr-review command with approve-and-stamp pages exists, but its enable check returns false.
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?
A large amount of new machinery for PR-review pages that can be approved and stamped is present but unreachable.
- Includes a prr-stamp island, a pinned stamp-control markup fragment, an approve script, and auto-react wiring on publish.
- Adds a
pr_review_startedtelemetry event tagged with lane composed or legacy. - A validator refuses stamped pages published outside the composed lane.
- The
/artifact-pr-reviewcommand's isEnabled resolves to a function that returns false, so nothing here is reachable. - The composed lane additionally sits behind
tengu_walnut_sconce, whose fallback is off.
approve-enabled review pages publish only through the composed lane
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.219
Republishing an artifact page now verifies it came from this CLI build
Both mention review
-
v2.1.219
PR-review artifact description has an alternate wording that cannot ship in this build
Both mention review
-
v2.1.238
Stricter check before republishing a PR-review page
Both mention review