You'll notice
Useful2 Signal3
Artifact wording swaps for live-files variants, and gateway reads now say when they are not enabled.
What's wrong with this entry?
Anonymous. No account, no email.
What
Artifact 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.
Details
- 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.
Evidence
"artifact reads through the session gateway are not enabled for this session"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.