Under the hood
Useful1 Signal2
On exit, the final transcript update goes through the storage layer first, falling back to a direct write.
What's wrong with this entry?
Anonymous. No account, no email.
What
On shutdown, the final transcript update is attempted asynchronously through the storage layer under a timeout, and falls back to the old synchronous write when that lapses or the layer is not in use.
Details
- The async path only runs when the newer storage backend is pinned on; otherwise the synchronous re-stamp is used directly.
- Timeouts are logged rather than silently swallowed.
- Exit lines belonging to another session are tracked so they are not appended twice.
- A new transcript record type,
artifact-autoreact-ledger, is registered as always persisted with last-write-wins.
Evidence
Exit re-stamp through the storage backend did not finish within
Strings lifted out of the shipped bundle, so the claim above can be checked against them.