Lots of session state now belongs to each session, which matters when several run in one process.
What's wrong with this entry?
State that was held in module-level singletons is now resolved per host: invoked skills, request latches, startup timing, event-logger state, the session registry, project-directory and temp-directory caches, artifact share probes and the token-reminder state. Behaviour is meant to be unchanged; it matters when several sessions run in one process.
memory-watcher: started with the storage interface
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.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state