[BUG] /goal clear typed while a goal is running is queued forever: the goal's Stop hook never lets the turn end

Environment: Claude desktop 2.26454.2 (Code tab), Claude Code 2.1.287, Windows 11

What happens
With an open-ended /goal active, typing /goal clear while Claude is working puts it in the queue (shown with "Send now"). Each time Claude tries to stop, the goal's Stop hook re-prompts it ("Hook re-prompted Claude"), so the turn never ends and the queued /goal clear never runs. In our case it sat in the queue for more than 3 minutes through several re-prompts, while Claude kept replying "waiting for you to clear the goal". It ran only after a manual interrupt.

Steps to reproduce

1. /goal keep on improving the project (any condition that is never met)
2. While Claude is working, type /goal clear and press Enter
3. The command stays queued, and Claude keeps being re-prompted by the goal

Expected
/goal clear takes effect right away. For example, it could skip the queue the way "Send now" does, or the goal's Stop hook could stop blocking while a /goal clear is queued.

Workaround
Click "Send now" under the queued message, which interrupts the turn and runs it at once. Or press Stop, then /goal clear.

Evidence from the transcript JSONL: queue-operation enqueue "/goal clear" at 22:35:05, then "Stop hook feedback: [<goal>]" rows at 22:35:17, 22:35:27 and later. The dequeue came only at 22:38:10, after a manual interrupt.