Remote transcript uploads track message ids, so compaction no longer loses or duplicates work.
What's wrong with this entry?
Uploading a session transcript to the remote side no longer decides what is new by comparing a stored index against the message count, which could miss or duplicate work after a compaction. It now anchors on message ids and tracks which it has already seen, logging when it detects that history was rewritten.
- Messages are counted as seen without being uploaded once the session binding has detached.
- Uploads of compaction pairs are skipped entirely for sessions carrying history-backfill suppression, with a log line saying so.
[persist-remote] Skipping compact-pair upload: session carries history-backfill suppression
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.