Live-edit would be blocked on workshop pages so changes go through the validating publish path.
Workshop live-edit refusals are wired with detection and messages but sit behind the same gate, off by default.
tengu_gable_onyx_sluice 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: 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.219. 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 Artifact tool blocks live-edit actions against workshop pages so edits go through the publish path that validates them.
- Target slug is checked against the session's known workshop slugs, then open frame URLs, then a server-side fetch looking for a
ws-decisionsisland. - A match refuses with
workshop_live_edit_refused; a transient read failure refuses withworkshop_live_edit_unverifiableand tells you to retry or WebFetch the page. - Same gate as the verifier:
Xde()/tengu_gable_onyx_sluice, fallback off.
live-edit is not available on workshop pages \u2014 edit the local workshop file and republish; the publish path is the validation chokepoint live-edit would bypass
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.