{"version":"2.1.229","anchor":"artifact-publish-can-demand-a-session-context-switched-off-h","canonical_anchor":"artifact-publish-can-demand-a-session-context-switched-off-h","heading":"Artifact publish can demand a session context, switched off here","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-publish-can-demand-a-session-context-switched-off-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact publish can demand a session context, switched off here\n\nPublishing an artifact could carry session context so a later session resumes it, but it's disabled.\n\n**What**\n\nPublishing an artifact gained an optional `session_context` parameter, an error when it is missing on a first publish, and capture of the prompt that triggered the publish (truncated with a marker) plus the model into the published metadata. It all sits behind a latch that is initialized to false in this build, so the parameter is never offered and the requirement never fires.\n\n**Details**\n\n- Error case is `session_context_required` on the first publish only\n- Latch has no code path in this build that sets it true\n\n**Evidence**\n\n`session_context_required`\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"}