Code exists to delete one record from a stored session by rewriting the stream.
Single-record deletion from a session transcript is implemented as the machinery a targeted deletion would need, with no surface described here.
What's wrong with this entry?
New code can delete a single record from a stored session by rewriting the stream in place, which is the machinery a targeted deletion would need.
- It walks records backwards looking for the target id in the raw bytes, then parses to confirm before rewriting.
- The rewrite is done in place with a precondition on the current version, retried up to three times if the stream changed underneath it.
- It stops and reports rather than looping if the stream exceeds a read budget or the backward cursor fails to move.
Tombstone removal abandoned: the backward record cursor did not advance
Strings lifted out of the shipped bundle, so the claim above can be checked against them.