Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.238,
Internal ChangesSection of the release
What
Appending 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.
Details
A tear is detected from a missing trailing newline or a torn byte count reported by the storage layer.
When the storage layer is not active, the append falls back to opening the file read-write/append and probing before writing.
Errors are classified, and recoverable ones note that the synchronous re-stamp runs instead.
Evidence
the synchronous re-stamp runs instead
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
