{"version":"2.1.239","anchor":"publish-conflicts-can-auto-read-the-live-artifact-first","canonical_anchor":"publish-conflicts-can-auto-read-the-live-artifact-first","heading":"Publish conflicts can auto-read the live artifact first","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/publish-conflicts-can-auto-read-the-live-artifact-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Publish conflicts can auto-read the live artifact first\n\nPublish conflicts could auto-fetch the live artifact first, and read-only collaborators get clearer advice.\n\n**What**\n\nWhen publishing an artifact hits a conflict, the client can automatically read the current live version and hand it back inline or as a saved file, and reports a specific reason when it will not. Read-only collaborators now get told plainly to publish as a new artifact instead. The whole path sits behind a helper whose default this build does not settle; when it is off, the guard records the reason `gate_off` and does nothing.\n\n**Details**\n\n- Refusal reasons include no batch, URL mismatch, read denied, no write access, reader persistence off, workshop schema, over cap, control bytes, read lag and persist failed.\n- Outcomes are reported through an `artifact_guard_autoread` event.\n\n**Evidence**\n\n`This session has read-only access to this artifact (it was shared for viewing, or it is someone else's public artifact), so it can never publish to it`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}