{"version":"2.1.234","anchor":"session-metadata-is-no-longer-written-into-the-wrong-transcr","canonical_anchor":"session-metadata-is-no-longer-written-into-the-wrong-transcr","heading":"Session metadata is no longer written into the wrong transcript","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/session-metadata-is-no-longer-written-into-the-wrong-transcr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Session metadata is no longer written into the wrong transcript\n\nSwitching sessions mid-write no longer lands metadata in the wrong transcript.\n\n**What**\n\nThe background step that re-appends session metadata now checks, after its await, whether the session file or session id changed while it was waiting, and bails out if so. Without that check a session switch mid-write could land metadata in the transcript you moved to.\n\n**Details**\n\n- The guard is opt-in through a new parameter on the re-append call, so existing callers choose whether the check applies.\n- The configuration cache now emits an `installed` event when a config is installed or written through, so other code can observe disk reads and writes.\n\n**Evidence**\n\n`reAppendSessionMetadataAsync`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}