Under the hood
Useful1 Signal2
Session storage is now passed explicitly through review, fork, compaction, team memory and config writes.
What's wrong with this entry?
Anonymous. No account, no email.
What
A wide set of call paths now receive the session storage handle as an argument rather than picking it up from ambient state: session review and fork, building compaction attachments, transcript copy, team-memory push and pull, skill partition checks, MCP pending-server prompts, message enqueue, theme and mode dialogs, and config setters such as the code-review effort write.
Details
- The tracker that watches whether the session file is writable moved onto the session store and is now handed to the pull-request link recorder instead of read from a module global.
- The module-level project-session accessor, along with the process
exithandler it registered, was removed.
Evidence
storageV5
Strings lifted out of the shipped bundle, so the claim above can be checked against them.