More cached state moved behind accessors so it can be reset per session or account.
What's wrong with this entry?
Promo campaign parsing, tmux colour application, a classifier warning latch, design MCP session and initialize caches, the passes eligibility request, the plan file cache and the plugin approved-plan map now read their state through getters, and the wake router and monitor socket task take their dependencies as arguments. Nothing changes for a user; these caches can now be reset per session or account.
e.initializeInFlight = n;
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.236
Process-wide state replaced by per-session containers
Both mention state
-
v2.1.236
Agent, MCP and UI caches scoped per session
Both mention state
-
v2.1.236
The command queue is now passed around instead of being a global
Both mention state