Summary

• allow durable cron recovery to repair terminal lost cron task rows when the loss was the backing-session-missing false-positive path
• keep recovery constrained to cron rows whose lost error is empty or mentions backing session missing, so unrelated lost terminal rows are not rewritten
• add regression coverage for terminal lost cron recovery and non-backing-session lost rows staying unchanged
• add an Unreleased changelog entry for the user-facing task maintenance recovery behavior

Related #63196
Related #72884
Related #68191

Real behavior proof

• Behavior or issue addressed: Cron-backed task rows that were already terminal/lost because the registry falsely concluded the backing session was missing can now be recovered from durable cron run state/logs, while unrelated lost terminal rows stay unchanged.
• Real environment tested: Local OpenClaw checkout on macOS, PR branch head 38c58fc92115b830433ae5f6962d5a400ccbc48f, Node v24.5.0, pnpm 11.0.8. The current source CLI entrypoint from this checkout was run against an isolated temporary OPENCLAW_HOME and OPENCLAW_CONFIG_PATH; it did not touch the live user registry.
• Exact steps or command run after the patch: An isolated task registry sqlite was seeded through the real task registry APIs with a cron task row:
  • runtime: "cron"
  • status: "lost"
  • error: "backing session missing"
  • runId: "cron:cron-proof-terminal-lost:<startedAt>"
  • matching durable cron run log entry with action: "finished", status: "ok", runAtMs: <startedAt>, and summary: "proof recovered from durable cron run log"
• Commands run after the patch:

  OPENCLAW_HOME="$PROOF_HOME" \
  OPENCLAW_CONFIG_PATH="$PROOF_HOME/.openclaw/openclaw.json" \
  node --import tsx /private/tmp/openclaw_pr75036_current_proof/seed-terminal-lost-cron-proof.mjs
  
  OPENCLAW_HOME="$PROOF_HOME" \
  OPENCLAW_CONFIG_PATH="$PROOF_HOME/.openclaw/openclaw.json" \
  node --import tsx src/index.ts tasks maintenance --json
  
  OPENCLAW_HOME="$PROOF_HOME" \
  OPENCLAW_CONFIG_PATH="$PROOF_HOME/.openclaw/openclaw.json" \
  node --import tsx src/index.ts tasks maintenance --apply --json
  
  OPENCLAW_HOME="$PROOF_HOME" \
  OPENCLAW_CONFIG_PATH="$PROOF_HOME/.openclaw/openclaw.json" \
  node --import tsx src/index.ts tasks list --json
  
  node scripts/test-projects.mjs src/tasks/task-registry.test.ts src/tasks/task-registry.maintenance.issue-60299.test.ts
  git diff --check

• Before evidence: The seeded isolated registry contained a terminal lost cron row:

  {
    "runtime": "cron",
    "sourceId": "cron-proof-terminal-lost",
    "status": "lost",
    "error": "backing session missing",
    "runId": "cron:cron-proof-terminal-lost:1778567791974"
  }

• Evidence after fix: Copied live terminal output from the current source CLI preview and apply commands; both reported durable cron recovery:

  {
    "mode": "apply",
    "maintenance": {
      "tasks": {
        "reconciled": 0,
        "recovered": 1,
        "cleanupStamped": 0,
        "pruned": 0
      }
    },
    "tasks": {
      "total": 1,
      "terminal": 1,
      "failures": 0,
      "byStatus": {
        "succeeded": 1,
        "lost": 0
      },
      "byRuntime": {
        "cron": 1
      }
    }
  }

• Observed result after fix: Copied live terminal output from tasks list --json showed the same task recovered to succeeded and the stale backing-session error was gone:

  {
    "runtime": "cron",
    "sourceId": "cron-proof-terminal-lost",
    "status": "succeeded",
    "terminalSummary": "proof recovered from durable cron run log"
  }

• Supplemental targeted verification after the patch:

  Test Files  2 passed (2)
  Tests  83 passed (83)
  
  git diff --check completed without whitespace errors.
  

• What was not tested: Did not run tasks maintenance --apply against the live user task registry; the real command was run against a seeded isolated registry only.

Test plan

• node scripts/test-projects.mjs src/tasks/task-registry.test.ts src/tasks/task-registry.maintenance.issue-60299.test.ts
• git diff --check