[Bug] ScheduleWakeup accepts calls outside /loop context without validation

Bug Description
Type: Bug Title: ScheduleWakeup accepted a call outside /loop context Area: (none specified) Details: - What happened: I called ScheduleWakeup to wait for a background poll task, even though this session was never in /loop mode. The tool's own description says it's specifically for /loop dynamic-pacing mode, but it accepted the call anyway and returned a normal "Next wakeup scheduled" confirmation with no warning that this wasn't a /loop session. - What the user said: User didn't comment; observed by the model mid-task. - Repro: In a normal (non-/loop) interactive session, with a background Bash task already running (via run_in_background), call ScheduleWakeup with a delaySeconds/reason/prompt/noop instead of just waiting for the background task's own completion notification. - Cause: I should have just relied on the background task notification (which already fires automatically when a backgrounded Bash command finishes) instead of reaching for ScheduleWakeup, which is scoped to a different feature. The tool gave no signal that it was being misused outside its intended context. ---

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.283
• Feedback ID: 45bee835-13ea-49b8-a0cb-712adbb82713

Errors

[]