{"version":"2.1.242","anchor":"artifact-live-files-wording-and-a-distinct-gateway-refusal","canonical_anchor":"artifact-live-files-wording-and-a-distinct-gateway-refusal","heading":"Artifact live-files wording and a distinct gateway refusal","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifact-live-files-wording-and-a-distinct-gateway-refusal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifact live-files wording and a distinct gateway refusal\n\nArtifact wording swaps for live-files variants, and gateway reads now say when they are not enabled.\n\n**What**\n\nArtifact result suffixes, the explanation of the `path` argument and publish-change detection now have alternate live-files wordings picked at runtime, and reads through the session gateway can fail with an explicit \"not enabled for this session\" message rather than a generic transport error. Creating an Artifact from a type is refused in cloud sessions.\n\n**Details**\n\n- The live-files wording is chosen by a runtime capability check derived from the tool's shape rather than a named flag, so which variant you see depends on what the session reports rather than on any setting in this build.\n\n**Evidence**\n\n`\"artifact reads through the session gateway are not enabled for this session\"`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}