Publishing or handing over an artifact now checks whether its source changed since it was last read, instead of assuming it's still current
What
- The artifact hand-over/auto-read guard now checks whether the source changed since it was last read; if so, it returns a new outcome,
own_version_source_changed, instead of silently proceeding on the client's own version. - The set of reasons an artifact or page can be withheld now includes a new
sourceChangedreason, alongside existing ones likegoneandotherOrg. - When publishing an update, if the current file is recorded as this session's own source for that artifact, its recorded version matches what's live, and it hasn't been read as a "workshop page", publishing now proceeds without forcing a fresh stale-version check, and logs telemetry for that auto-proceed decision.
Why
This prevents Claude Code from silently overwriting an artifact whose source has actually changed elsewhere, while still allowing a fast republish when republishing your own unchanged work.
tengu_sorrel_trellis_tenon 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.271: 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.271. It isn't a statement about your account. What a flag value here can and cannot tell you