{"version":"2.1.269","anchor":"transcript-compaction-now-tracks-host-injected-rows-separate","canonical_anchor":"transcript-compaction-now-tracks-host-injected-rows-separate","heading":"Transcript compaction now tracks host-injected rows separately when reordering","tier":"internal","area":"Compaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/transcript-compaction-now-tracks-host-injected-rows-separate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Transcript compaction now tracks host-injected rows separately when reordering\n\nTranscript compaction now keeps host-injected messages next to the conversation turn they belong to\n\n**What**\n\nThe internal message-log handling gained a way to mark certain rows as \"host-injected\" (`appendHostRows`\/`isHostRow`), tracked with a `WeakSet`. A new reordering step now runs before a compaction boundary (the point where old conversation history gets summarized to save space) is applied, moving these host-injected rows so they sit next to the assistant or user turn they belong with.\n\n**Why**\n\nThis should prevent host-injected messages from ending up separated from their related conversation turn when the transcript is compacted, keeping the summarized history coherent.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}