Conflict auto-read sits behind a helper whose default the build does not settle, recording gate_off when disabled.
When 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.
- 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.
- Outcomes are reported through an
artifact_guard_autoreadevent.
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
Strings lifted out of the shipped bundle, so the claim above can be checked against them.