{"version":"2.1.242","anchor":"a-second-route-for-published-file-and-asset-reads","canonical_anchor":"a-second-route-for-published-file-and-asset-reads","heading":"A second route for published-file and asset reads","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/a-second-route-for-published-file-and-asset-reads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### A second route for published-file and asset reads\n\nPublished-file reads gained a second route via a capability lookup; failures explain the relay is unavailable.\n\n**What**\n\nThe check deciding whether published-file and asset reads can run is now satisfied by either the original condition or a new alternative that sits behind a capability lookup. When neither holds in a remote cloud session, the read fails as before with the relay reported unavailable, and its long explanation now lives in shared constants.\n\n**Details**\n\n- What turns the second condition on is decided by that capability lookup rather than by anything set in this build.\n\n**Evidence**\n\n`relay_unavailable`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}