permissions.defaultMode: "bypassPermissions" doesn't prevent a fresh session from starting in "manual mode" — Scheduled Tasks still hit Allow prompts

Environment: Claude Code v2.1.227, Windows

What I configured: In .claude/settings.local.json, I set permissions.defaultMode: "bypassPermissions" and top-level skipDangerousModePermissionPrompt: true, expecting this to eliminate Allow prompts for a daily recurring Scheduled Task that runs fully unattended (nobody present to click Allow).

What actually happens: Despite that config being confirmed present and unchanged, a fresh interactive window opened directly in that same project still starts with the bottom-bar mode indicator showing "manual mode on" — not bypass. Shift+Tab can manually cycle it to "auto mode" / "accept edits on" mid-session, but this is a live, per-window, keyboard-driven toggle that doesn't appear to be set from settings.json's defaultMode at session start.

Separately, I checked the create_scheduled_task/update_scheduled_task tool schemas directly — neither has any permissionMode field. create_scheduled_task's own description says: "an approval prompt may or may not appear depending on the user's permission settings, so don't rely on it as the confirmation step" — acknowledging the gap without a resolution.

Impact: There's no reliable way to make a Scheduled Task truly unattended — it can still hit an Allow prompt with nobody there to answer it, stalling the run indefinitely.

Request: either make permissions.defaultMode actually govern the starting mode for Scheduled-Task-spawned sessions, or add an explicit permission-mode parameter to create_scheduled_task/update_scheduled_task.