You'll notice
Useful3 Signal2
Resuming another conversation mid-upload no longer attaches the old session's transcript.
What's wrong with this entry?
Anonymous. No account, no email.
/resume
What
If you resume a different conversation while a transcript backfill is still running, the upload now aborts and logs instead of pinning content from the old session onto the live one. The check runs both before the main upload and before the subagent pass.
Evidence
[persistence-sync] Refusing backfill: session id changed since the scan anchor was pinned
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.
-
v2.1.223
--resume-session-at help text clarified to chain entries
Both mention resume
-
v2.1.232
Resuming with an unrecognisable session id now forks instead of resuming
Both mention resume
-
v2.1.239
Resume hints no longer point at directories that are gone
Both mention resume