Recovering a stray background agent entry now records that it happened, so gaps are traceable.
What's wrong with this entry?
Seeding an orphaned background-agent roster entry through the storage backend now emits an event when the seed succeeds.
- the seed is an
ifAbsentwrite - an
AlreadyExistserror is treated as benign and ignored; other errors are reported
tengu_bg_roster_orphan_adopted
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.227
Deleting a background job keeps a directory a live session is sitting in
Both mention background
-
v2.1.248
claude logsno longer lets replayed output corrupt your terminalBoth mention background
-
v2.1.248
Job list offers "open" rather than "resume" for a job already attached to a terminal
Both mention background