Queue approval prompts so a parallel run is not stranded forever

[Seungpyo1007]

The bug

askRunApproval stored its resolve in a single field:

this._askRunResolve = resolve;
this.setState({ askRun: { command, rationale, agent, ... } });

That holds only while one run exists. This app runs several at once — a round with two delegate_task calls starts two sub-runs in parallel (flying in runAgentTurn), and either can hit the shell-command or game-engine approval gate.

When two gates land, the second overwrites the first's resolve. Answering the dialog settles only the second. The first run stays parked on await forever:

• its agent is stuck at status edit,
• the finally that releases fileLocks is never reached, so other agents asking for that file keep hearing "another agent is working on it",
• nothing is shown to the user. There is no error, no timeout, no way back except restarting.

The fix

src/engine/askQueue.ts queues them: show one, resolve the one that was answered, then raise the next. The invariant is that every request settles exactly once.

Stopping an agent now also drops that agent's queued requests, not just the visible one — otherwise a stopped agent's dialog resurfaces later while its run stays parked. Stop-all rejects the whole queue.

Verification

• 9 unit tests on the queue, including the overwrite case that used to strand the first request. 963 passing (was 954).
• npm run typecheck clean.
• Real-app regression probe (open/edit/external-change/save): 5/5.

Scope note: the collision needs two live model runs to reproduce end-to-end, so it is covered by unit tests rather than a CDP probe. The real-app run here checks that the single-dialog path did not regress.