You'll notice
Useful2 Signal3
Transcripts belonging to another account are marked so history never quietly reappears later.
What's wrong with this entry?
Anonymous. No account, no email.
What
When the session bridge blocks saving a transcript because it belongs to a different account, that fact is now written into the transcript itself as a history-suppression record and the session id is marked in memory. Forks of the session inherit the suppression, and the background backfill refuses to restore any transcript carrying the record, so cross-account history can no longer creep back in later.
Details
- backfill also refuses a transcript whose scan for the marker runs past its line budget, erring toward not restoring
- a half-written entry pair seen during resume takes a weaker in-memory suppression only, with no permanent marker written
- reported as
rc_cross_account_suppression
Evidence
[persistence-sync] Refusing backfill: history-suppression entry in transcript
Strings lifted out of the shipped bundle, so the claim above can be checked against them.