{"version":"2.1.239","anchor":"republishing-a-page-the-session-has-not-read-gives-a-clearer","canonical_anchor":"republishing-a-page-the-session-has-not-read-gives-a-clearer","heading":"Republishing a page the session has not read gives a clearer refusal","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/republishing-a-page-the-session-has-not-read-gives-a-clearer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Republishing a page the session has not read gives a clearer refusal\n\nRefusals to overwrite an artifact you haven't read now tell you which case you hit.\n\n**What**\n\nThe guard that stops Claude overwriting an artifact with stale content now reports which situation it hit, including a new refusal when the model resends byte-identical content that was already rejected, and a separate one when a sibling agent read the live version earlier in the same turn.\n\n**Details**\n\n- The old helper that quietly auto-read and reseeded the version (reporting outcomes like a gate being off or a cap being exceeded) was removed.\n- Refusals now come from either the local guard or a 409 from the server, and telemetry labels which of the two fired.\n\n**Evidence**\n\n`stale_version_guard_seeded`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}