Artifacts (@kirocrew-core/artifact_*)

A widget rendered inline in chat (<mcwidget>) is auto-registered as an unpinned artifact when its response segment finalizes, a record, not a library entry: unpinned auto-registered widgets are pruned oldest-first, and widgets from an incognito or temporary session are never registered at all.

Saving and pinning are two different things. artifact_save creates a named, durable artifact: it is never swept, because the sweep only ever considers auto-registered records. Pinning is the separate star (pinned, false by default) the user flips in chat or the library; it is what takes an auto-registered widget out of the sweep, and it is not something a save does for you. Either way the artifact has a stable identity, a version history, and a URL the user can open from /artifacts/<slug> in the dashboard.

Artifacts exist so the user can build a library of durable, named work, useful UIs (CR queue, pipeline health, ticket triage, dashboards) and substantial documents (plans, design docs, analyses, reports) alike, to return to, iterate on across sessions without losing prior versions, or share with peers for feedback. The library is curated: it holds work worth keeping, not a mirror of every file or a copy of the chat.

Dynamic Dashboards for long work

The host's opt-in automatic session cards are separate from saved artifacts: session events trigger bounded updates from that session's recent messages, without a conductor publishing on its behalf. The model can reuse a card's HTML layout and update only text data. Runtime state, Needs you, and exact-session answers/approvals belong to the host. Polling an artifact is not a card-generation trigger. Use the saved-view flow below for a durable, task-specific publication, not to imitate those controls or keep every session's status alive.