Publishing over a stale artifact now fetches the current version so Claude can merge and retry.
tengu_cobalt_plinth_moss Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.227: 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.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Previously a publish was refused when your session had not seen the latest version of a page you were about to overwrite. Claude can now fetch the live page itself, count it as viewed, and hand it back inline with instructions to merge your changes and republish. It applies only to pages you own that nobody else is co-writing, and only under a size cap and a read timeout.
- Controlled by
tengu_cobalt_plinth_moss, which falls back to on when no remote value is present. - A successful auto-read raises
stale_version_guard_seeded; the page is returned in full for you to merge. - Refusals are logged under
artifact_guard_autoreadwith a reason:gate_off,over_cap,read_timeoutorsibling_in_flight. - Pages containing control bytes are rejected rather than read.
artifact_guard_autoread
Strings lifted out of the shipped bundle, so the claim above can be checked against them.