You'll notice
Useful3 Signal3
SessionEnd hooks get five seconds instead of 3.5, and the transcript is sealed at exit.
What's wrong with this entry?
Anonymous. No account, no email.
SessionEnd
What
The failsafe timer that forces exit after shutdown begins grew from 3.5 seconds to 5 seconds at both places it is armed, giving SessionEnd hooks more slack. Shutdown can now also seal the session file against further appends, after which both local and remote persistence stop early, and a single final owed entry is written straight to the session file.
Details
- The seal is one-way for the remainder of the process.
- The final-entry write replaces the previous exit re-stamp helper.
- Unconditional; no flag.
Evidence
sealAppendsForShutdown
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.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.238
Reconnecting an SDK host swaps its hooks in and settles the ones left waiting
Both mention hook
-
v2.1.238
Hook callbacks remember which host created them
Both mention hook