Not switched on
Useful2 Signal4
Publishing an artifact could carry session context so a later session resumes it, but it's disabled.
A session_context parameter, its missing-context error, and prompt/model capture are behind a latch initialised false.
What's wrong with this entry?
Anonymous. No account, no email.
What
Publishing 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.
Details
- Error case is
session_context_requiredon the first publish only - Latch has no code path in this build that sets it true
Evidence
session_context_required
Strings lifted out of the shipped bundle, so the claim above can be checked against them.