More code paths hold the message queue directly instead of reaching for a global.
What's wrong with this entry?
The print loop, agent config builder, goal-proposal handling and query-context rebuilder now hold a queue handle and call its enqueue, peek and match-and-drain methods instead of module-level wrappers around a single global queue. No behaviour change.
dequeueAllMatching
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.232
Command queue is a single adoptable instance
Both mention queue