Workshop doc snapshotting and permissions sit behind tengu_larch_pavise, fallback false, with tengu_cedar_transom as a kill-switch.
The per-session *.workshop.md document is now snapshotted with the rest of the session files and gets explicit read and write permission handling, all behind the workshop gate.
- gated on the workshop feature gate, combining
tengu_larch_pavise(fallback false) withtengu_cedar_transomas a kill-switch - the doc is included in the file-snapshot system entry under the key "workshop"
- it is skipped with a log line when it exceeds the snapshot character cap, and skipped when unchanged
- write permission for
<session>.workshop.mdis granted via anincludeWorkshopDocoption only when the caller's permission mode isplan, with the mode newly threaded into that check - the read side always includes it, so "Plan files for current session are allowed for reading" covers the workshop doc unconditionally
- publishing a plan records the returned slug in
workshopVerifiedSlugsapp state
Workshop doc over snapshot cap, Plan files for current session are allowed for writing
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_larch_pavise Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.219: 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.
tengu_cedar_transom 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.219: 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.
Read once, for one account on one subscription tier, against v2.1.219. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: tengu_cedar_transom