Prompts can carry a wait marker that queues behind the current turn, but nothing sets it.
A wait flag runs end to end through prompt submission with no caller setting it in this build.
What's wrong with this entry?
Submitting a prompt can now carry a "wait" marker that follows the prompt through queuing and into the query pipeline, and that lets an otherwise-empty submission through instead of being discarded as a no-op. Nothing in this build turns it on, so no user action reaches it yet.
- The flag defaults to false at every point it is read.
- Without it, an empty submission is still dropped and recorded as an empty prompt submit.
runPromptSubmitChain
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