{"version":"2.1.238","anchor":"transcript-appends-repair-a-truncated-last-line","canonical_anchor":"transcript-appends-repair-a-truncated-last-line","heading":"Transcript appends repair a truncated last line","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/transcript-appends-repair-a-truncated-last-line","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Transcript appends repair a truncated last line\n\nA crash mid-write no longer corrupts your transcript; the truncated line is repaired on the next append.\n\n**What**\n\nAppending to a transcript now detects a last line that was cut off mid-write and writes a leading newline plus a substitute record before adding the new one, so a crash mid-append no longer corrupts what follows.\n\n**Details**\n\n- A tear is detected from a missing trailing newline or a torn byte count reported by the storage layer.\n- When the storage layer is not active, the append falls back to opening the file read-write\/append and probing before writing.\n- Errors are classified, and recoverable ones note that the synchronous re-stamp runs instead.\n\n**Evidence**\n\n`the synchronous re-stamp runs instead`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 2\/5"}