{"version":"2.1.236","anchor":"session-logs-gained-a-versioned-record-for-watched-artifacts","canonical_anchor":"session-logs-gained-a-versioned-record-for-watched-artifacts","heading":"Session logs gained a versioned record for watched Artifacts","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/session-logs-gained-a-versioned-record-for-watched-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Session logs gained a versioned record for watched Artifacts\n\nWhich Artifacts a session watches for comments is now a versioned session-log record, cleared on fork.\n\n**What**\n\nWhich Artifacts a session watches for comments is stored as its own session-log entry with a schema and a version number, replayed as last-wins when session state is rebuilt, and explicitly cleared when a session is forked or moved.\n\n**Details**\n\n- The record carries the session id and the list of Artifacts.\n- Whether the monitor itself is flagged is not visible here; the recording and replay plumbing runs unconditionally.\n\n**Evidence**\n\n`\"artifact-comment-monitor\": \"last-wins\",`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}