Resuming a session no longer installs a process-wide command queue; several globals are gone.
What's wrong with this entry?
The inbound peer-hold state, the local socket messaging state, the GitHub auth logger, computer-use call state and the activity tracker all lost their process-global form; the tracker's shared instance field became a looked-up reference. The command queue proxy and its socket dispatcher were deleted and the queue is passed as a plain value, so resuming a session no longer installs a process-wide queue.
resetInstance
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