fix(scheduler): restore cron job visibility via WS RPC

[moltar-bot]

Problem

Scheduler was not showing gateway cron jobs (only heartbeat jobs appeared).

Root cause

• /tools/invoke did not expose cron/cron.list on this gateway integration (404 Tool not available)
• jobs.json fallback was blocked by workspace path policy (PATH_NOT_ALLOWED on /cron/jobs.json)

Fix

• add gatewayWsRpc('cron.list', { includeDisabled: true }) fallback in cronList() before jobs.json fallback
• preserve existing fallback behavior and logging

Validation

• npm run -w ./api test:run -- openclawGatewayClient.test.js
• Local runtime verification after API rebuild:
  • GET /api/v1/openclaw/cron-jobs now returns gateway cron jobs + heartbeat jobs

[Copilot]

Pull request overview

Restores scheduler visibility of gateway cron jobs by adding a WebSocket RPC fallback to cronList() when /tools/invoke does not expose cron tooling and the jobs.json workspace fallback is blocked.

Changes:

• Add a new gatewayWsRpc('cron.list', { includeDisabled: true }) fallback in cronList() before the jobs.json fallback.
• Preserve existing behavior for /tools/invoke-based cron listing, including existing “service unavailable/not configured” graceful returns.
• Extend logging around the new fallback path.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[moltar-bot]

Addressed Codex review blocker ✅

• Updated cronList() fallback flow so WS RPC SERVICE_NOT_CONFIGURED / SERVICE_UNAVAILABLE no longer returns early.
• It now continues to jobs.json fallback for max compatibility.
• Updated logging/messages + docblock to reflect actual fallback order.
• Updated unit expectation in openclawGatewayClient.test.js.

Validation:

• npm run -w ./api test:run -- openclawGatewayClient.test.js (pass)