{"version":"2.1.227","anchor":"republishing-a-stale-artifact-can-now-pull-in-the-current-ve","canonical_anchor":"republishing-a-stale-artifact-can-now-pull-in-the-current-ve","heading":"Republishing a stale artifact can now pull in the current version for you","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/republishing-a-stale-artifact-can-now-pull-in-the-current-ve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Republishing a stale artifact can now pull in the current version for you\n\nPublishing over a stale artifact now fetches the current version so Claude can merge and retry.\n\n**What**\n\nPreviously 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.\n\n**Details**\n\n- Controlled by `tengu_cobalt_plinth_moss`, which falls back to on when no remote value is present.\n- A successful auto-read raises `stale_version_guard_seeded`; the page is returned in full for you to merge.\n- Refusals are logged under `artifact_guard_autoread` with a reason: `gate_off`, `over_cap`, `read_timeout` or `sibling_in_flight`.\n- Pages containing control bytes are rejected rather than read.\n\n**Evidence**\n\n`artifact_guard_autoread`\n\n- Flag `tengu_cobalt_plinth_moss`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.227; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}