Remote Control does not connect for sessions started by scheduled tasks
Remote Control works correctly for an interactive session I start myself and manually enable it on. However, sessions spawned by a Scheduled Task (background/cron-triggered) always report remoteControlState: "off" -- even after enabling the account-level default "Connect new sessions to Remote Control." This means PushNotification calls from within a scheduled-task session never reach the paired mobile app, since they are always skipped with a "Remote Control is disabled/unavailable" result, regardless of org policy or the account default. Expected: scheduled-task sessions should respect the "Connect new sessions to Remote Control" default the same way manually-started sessions do, so background automations can actually notify the user's phone.