bug(runtime): ScheduledTask gives the model no clock, so relative schedules fall back to Bash

[liugddx]

What happened

Asked to "create a scheduled task at 10:00 today", the agent could not turn that into ScheduledTask's schedule.runAt, which takes epoch milliseconds. Nothing in the system prompt or in the ScheduledTask tool gives the model the current time or the Host time zone, so the model tried to read the clock with a shell:

return await tools.Bash({ command: "Get-Date -Format 'yyyy-MM-dd HH:mm:ss zzz'" });

{ "ok": false, "error": { "kind": "tool_failure", "message": "Command sandbox is required but unavailable on platform win32." } }

On Windows, Bash fails closed under any permission profile that requires a command sandbox (explore and ask; builtin-tools.ts, #2961). So a one-shot schedule relative to "now" depends on an unrelated capability that is unavailable on a supported platform, and scheduling itself never needed a shell.

The model reported, correctly, that reading the clock "should not be a prerequisite of Maka's scheduling capability".

How to reproduce

1. On Windows, use ask (default) or explore permission mode.
2. Ask the agent: "create a scheduled task at 10:00 today to …".
3. Observe the agent calling Bash to read the date and failing with Command sandbox is required but unavailable on platform win32.

Environment

• Maka Desktop 0.2.0-dev.48.20260923 (packaged)
• Windows 10 x64 (10.0.19042)
• Verified against source at apache/main@fef5b937a

Logs, screenshots, or additional context

Observed together with #5664 in the same session; the two are independent. Making the Host clock available from ScheduledTask itself (rather than from the system prompt) keeps the prompt cache stable.