Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.227,
What probably matters to youSection of the release
What
A new transcript entry marks a session whose earlier history was suppressed, most often because the signed-in account changed. Replay skips it, and remote sync refuses to backfill or upload the merged pair produced by compaction for any conversation carrying that mark.
Details
The record holds a session id, a cause and optionally the account it was vetoed against; duplicate detection for it uses only the type and session id.
Session state gained matching flags, surfaced to forks so a branched conversation inherits the suppression.
Evidence
[persistence-sync] Refusing backfill: conversation carries a history-suppression taint, [persist-remote] Skipping compact-pair upload: conversation carries a history-suppression taint
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
