fix(cron): auto-migrate legacy cron store by MonkeyLeeT · Pull Request #90208 · openclaw/openclaw

MonkeyLeeT · 2026-06-04T06:59:25Z

Summary

Add a non-interactive cron migration path that runs during doctor config preflight.
Share the existing doctor cron repair implementation between doctor --fix and non-interactive preflight so legacy JSON cron jobs are merged into the SQLite store through one repair path.
Keep existing SQLite rows as the winner for duplicate job ids, normalize legacy persisted cron shapes before writing, and archive legacy cron files only after the SQLite write succeeds.
Trimmed out the earlier foreground gateway run fast-path and read-only/status startup-detection hardening; this PR now stays scoped to the original legacy cron migration issue.

Root Cause

Cron runtime now reads and writes the canonical SQLite-backed store only. The existing doctor cron repair flow could import legacy jobs.json / jobs-state.json, but ordinary doctor config preflight did not call that cron migration before Gateway startup/restart paths touched runtime state. This meant legacy cron JSON files could remain present while the SQLite cron table stayed empty or incomplete.

Verification

git diff --check
node scripts/run-vitest.mjs src/commands/doctor/cron/index.test.ts src/commands/doctor-config-preflight.state-migration.test.ts src/cron/store.test.ts src/cli/program/config-guard.test.ts src/cli/run-main.exit.test.ts src/cli/run-main.test.ts
node --import tsx /private/tmp/openclaw-cron-preflight-proof.mjs
.agents/skills/autoreview/scripts/autoreview --mode local --codex-bin /private/tmp/codex-autoreview-flex (one allowed draft-PR autoreview round, clean before later scope trimming; not rerun per local draft-PR guardrail)

GitHub CI for head ee962f7e2e9414728bce93626fcce52918734b0f: pending after simplification push.

Real behavior proof

Behavior addressed: legacy cron jobs are migrated into SQLite during doctor config preflight before Gateway runtime reads the SQLite-only cron store.

Real environment tested: local macOS source checkout using a throwaway OPENCLAW_HOME, source-aware scripts/run-node.mjs, direct source import of runDoctorConfigPreflight, real loopback Gateway readback, and a representative legacy cron store with jobs.json, split jobs-state.json, and a legacy JSONL run log. The temp home path was redacted.

Exact steps or command run after this patch: node --import tsx /private/tmp/openclaw-cron-preflight-proof.mjs. The script wrote legacy cron files into an isolated temp home, ran runDoctorConfigPreflight({ migrateState: true }), queried state/openclaw.sqlite, then started a loopback Gateway through scripts/run-node.mjs gateway run and called cron status --json plus cron list --all --json through the Gateway.

Evidence after fix:

{
  "before": {
    "legacyJobsJsonCount": 3,
    "legacyJobsStateCount": 3,
    "sqliteCronJobsRows": 0
  },
  "preflight": {
    "migratedSqlite": {
      "cronJobs": 3,
      "cronRunLogs": 1,
      "jobs": [
        { "jobId": "legacy-disabled-past", "enabled": 0, "scheduleKind": "at", "runningAtMs": null },
        { "jobId": "legacy-due-every", "enabled": 1, "scheduleKind": "every", "runningAtMs": null },
        { "jobId": "legacy-future-at", "enabled": 1, "scheduleKind": "at", "runningAtMs": null }
      ]
    },
    "archives": {
      "jobsJsonMigrated": true,
      "jobsStateMigrated": true,
      "legacyRunLogMigrated": true
    }
  },
  "afterGatewayStart": {
    "cronStatus": { "enabled": true, "jobs": 3 },
    "cronListAll": [
      { "id": "legacy-due-every", "enabled": true, "scheduleKind": "every", "lastRunStatus": "ok" },
      { "id": "legacy-future-at", "enabled": true, "scheduleKind": "at", "deliveryMode": "webhook" },
      { "id": "legacy-disabled-past", "enabled": false, "scheduleKind": "at", "deliveryMode": "webhook" }
    ],
    "sqlite": { "cronJobs": 3, "cronRunLogs": 2 }
  }
}

Observed result after fix: preflight converted the three legacy jobs into three SQLite cron_jobs rows, imported one legacy run-log row, and archived jobs.json, jobs-state.json, and the legacy run-log file. After Gateway startup, cron status reported jobs: 3, cron list --all returned all three jobs, legacy notify: true rows were converted to webhook delivery, and the overdue recurring job caught up once with lastRunStatus: "ok" while leaving runningAtMs: null.

What was not tested: a packaged 2026.5.28-to-PR-head install upgrade with a real user's cron store, and an actual gateway restart service-manager invocation. The service lifecycle command was not run locally because it can mutate launchd/systemd state; the proof exercises the same doctor config preflight hook and then verifies Gateway runtime readback from SQLite.

clawsweeper · 2026-06-04T07:01:09Z

Codex review: needs maintainer review before merge. Reviewed June 5, 2026, 1:18 PM ET / 17:18 UTC.

Summary
The PR adds a non-interactive legacy cron repair call to doctor config preflight and refactors doctor cron repair so prompted doctor and preflight share the same migration path.

PR surface: Source +107, Tests +12. Total +119 across 3 files.

Reproducibility: yes. by source inspection: v2026.6.1 and current main load cron jobs from SQLite and do not call cron repair from config preflight, so legacy JSON-only cron jobs can remain invisible until doctor repair runs. The linked issue also provides a concrete 2026.5.28 to 2026.6.1 upgrade symptom.

Review metrics: 1 noteworthy metric.

Automatic migration hooks: 1 non-interactive cron repair call added. This is the maintainer-relevant behavior change: preflight can now mutate persistent cron state before runtime commands read it.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

[P2] Add packaged upgrade or service-manager restart proof if maintainers want to reduce the remaining compatibility uncertainty before merge.

Risk before merge

[P1] This PR makes ordinary valid-config preflight write SQLite cron rows and archive legacy cron files before an operator explicitly runs doctor --fix, so maintainers need to accept that upgrade behavior.
[P1] Restored overdue recurring jobs may catch up after Gateway startup and trigger webhook or channel delivery side effects that users did not see while the jobs were missing.
[P1] The supplied proof is strong source-checkout and loopback Gateway proof, but it is not a packaged v2026.5.28-to-PR-head upgrade or real service-manager restart proof.

Maintainer options:

Accept the automatic cron migration policy (recommended)
If maintainers agree that preserving legacy cron jobs during preflight outweighs the automatic write/archive and catch-up side effects, the current patch is a bounded fix path.
Ask for packaged upgrade proof first
Require a packaged v2026.5.28-to-PR-head upgrade or service-manager restart smoke before merge to reduce uncertainty around the real upgrade path.
Keep migration behind explicit doctor repair
Pause or close this PR if maintainers want legacy cron recovery to remain an operator-initiated doctor --fix action rather than an automatic preflight repair.

Next step before merge

[P2] Needs human maintainer acceptance of compatibility-sensitive automatic cron migration and restored-job catch-up behavior; there is no narrow automated repair to request.

Security
Cleared: The diff touches cron migration code and tests only; I found no new CI, dependency, secret-handling, package-resolution, or third-party code-execution concern.

Review details

Best possible solution:

Land a doctor-owned, non-interactive cron migration only after maintainers explicitly accept the automatic upgrade semantics and the restored-job catch-up behavior.

Do we have a high-confidence way to reproduce the issue?

Yes, by source inspection: v2026.6.1 and current main load cron jobs from SQLite and do not call cron repair from config preflight, so legacy JSON-only cron jobs can remain invisible until doctor repair runs. The linked issue also provides a concrete 2026.5.28 to 2026.6.1 upgrade symptom.

Is this the best way to solve the issue?

Yes, this is an acceptable owner-boundary fix because legacy compatibility stays in doctor migration code while runtime continues to read the canonical SQLite store. It still needs maintainer acceptance because the chosen solution makes that repair automatic during preflight.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 4752e9a67d4f.

Label changes

Label changes:

add merge-risk: 🚨 message-delivery: Restoring overdue cron jobs can cause catch-up webhook or channel deliveries after Gateway startup.
add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix live output from a local source checkout and loopback Gateway showing legacy cron files migrated into SQLite, archived, and read back through cron status/list.

Label justifications:

P1: The linked regression loses persisted cron jobs on upgrade and affects a real user workflow, so the PR is urgent even though the remaining decision is compatibility acceptance.
merge-risk: 🚨 compatibility: The PR changes upgrade behavior by automatically writing SQLite cron rows and archiving legacy cron files during ordinary preflight.
merge-risk: 🚨 message-delivery: Restoring overdue cron jobs can cause catch-up webhook or channel deliveries after Gateway startup.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body includes after-fix live output from a local source checkout and loopback Gateway showing legacy cron files migrated into SQLite, archived, and read back through cron status/list.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix live output from a local source checkout and loopback Gateway showing legacy cron files migrated into SQLite, archived, and read back through cron status/list.

Evidence reviewed

PR surface:

Source +107, Tests +12. Total +119 across 3 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	2	225	118	+107
Tests	1	12	0	+12
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	3	237	118	+119

What I checked:

Current main preflight still omits cron migration: On current main, runDoctorConfigPreflight computes baseConfig and then only calls autoMigrateLegacyState or task sidecar migration; there is no cron repair call before runtime-facing commands proceed. (src/commands/doctor-config-preflight.ts:175, 4752e9a67d4f)
PR head adds the non-interactive cron preflight hook: The proposed head calls repairLegacyCronStoreWithoutPrompt when the config snapshot is valid, before the existing legacy state migration step. (src/commands/doctor-config-preflight.ts:184, f5aa1b67595b)
PR head keeps legacy cron repair in doctor-owned migration code: The refactor introduces loadLegacyCronRepairState, applyLegacyCronStoreRepair, and repairLegacyCronStoreWithoutPrompt in the doctor cron module, so runtime can remain SQLite-only while compatibility handling stays in doctor migration code. (src/commands/doctor/cron/index.ts:74, f5aa1b67595b)
Shipped v2026.6.1 has SQLite-only cron load without preflight cron repair: The latest release tag points at v2026.6.1; its preflight only runs generic state migration, and its cron store loader returns an empty store when SQLite has no cron rows, matching the linked upgrade-loss report. (src/cron/store.ts:63, 2e08f0f4221f)
Existing shipped repair path was interactive doctor health only: v2026.6.1 already had maybeRepairLegacyCronStore able to detect legacy cron files and merge legacy jobs, but that path was reached from doctor health rather than ordinary config preflight. (src/commands/doctor/cron/index.ts:55, 2e08f0f4221f)
CLI preflight is a broad command entry point: ensureConfigReady imports runDoctorConfigPreflight with migrateState: true for most state-migration-eligible CLI paths, so the PR changes upgrade behavior before commands such as gateway and cron read runtime state. (src/cli/program/config-guard.ts:171, 4752e9a67d4f)

Likely related people:

steipete: Current-main blame and history for the doctor cron repair, doctor config preflight, and SQLite cron store paths point to the recent current-main commit by Peter Steinberger. (role: recent area contributor; confidence: medium; commits: bafe17e60bcd; files: src/commands/doctor/cron/index.ts, src/commands/doctor-config-preflight.ts, src/cron/store.ts)
vincentkoc: The latest shipped v2026.6.1 commit by Vincent Koc contains the shipped doctor preflight and cron store behavior relevant to the upgrade regression. (role: release-path contributor; confidence: medium; commits: 2e08f0f4221f; files: src/commands/doctor/cron/index.ts, src/commands/doctor-config-preflight.ts, src/cron/store.ts)
jalehman: The GitHub timeline shows jalehman assigned to this PR, and the latest PR head is a branch merge commit authored by jalehman, making them a likely review-routing contact even though the code history points elsewhere. (role: current PR reviewer; confidence: low; commits: f5aa1b67595b; files: src/commands/doctor-config-preflight.ts, src/commands/doctor/cron/index.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

MonkeyLeeT · 2026-06-04T15:27:25Z

@clawsweeper re-review

Trimmed the PR scope and updated the PR body/proof for head ee962f7e2e9414728bce93626fcce52918734b0f.

The net diff now stays scoped to issue #90072 and is down to three files: it runs legacy cron migration during doctor config preflight and shares the existing doctor cron repair implementation between interactive doctor --fix and non-interactive preflight. The earlier foreground gateway run fast-path/bootstrap change, read-only/status startup-detection hardening, and the pass-through cron auto-migration wrapper were removed from the net PR diff.

Current proof includes git diff --check, focused Vitest coverage for the cron repair/preflight surface, and real behavior proof from node --import tsx /private/tmp/openclaw-cron-preflight-proof.mjs: legacy jobs.json, jobs-state.json, and run-log files were migrated into SQLite, archived after write, and then read back through a loopback Gateway with cron status and cron list --all.

clawsweeper · 2026-06-04T15:27:28Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

clawsweeper · 2026-06-04T16:40:51Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/26965787853
Updated: 2026-06-04T16:50:52.640Z

clawsweeper · 2026-06-04T20:11:35Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/26976789965
Updated: 2026-06-04T20:23:38.561Z

jalehman · 2026-06-05T17:22:09Z

Merged via squash.

Prepared head SHA: f5aa1b67595b72f6a2f30f899a1efedb1b01a377
Merge commit: 21aa297434e4f89b5e60aac88ab11929a7bfdf6b

Thanks @MonkeyLeeT!

@jalehman

Merged via squash. Prepared head SHA: f5aa1b6 Co-authored-by: MonkeyLeeT <6754057+MonkeyLeeT@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman

@jalehman

Merged via squash. Prepared head SHA: f5aa1b6 Co-authored-by: MonkeyLeeT <6754057+MonkeyLeeT@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman

@jalehman

Merged via squash. Prepared head SHA: f5aa1b6 Co-authored-by: MonkeyLeeT <6754057+MonkeyLeeT@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman

…26.6.5) (#963) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.1` → `2026.6.5` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.5`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202665) [Compare Source](openclaw/openclaw@v2026.6.1...v2026.6.5) ##### Highlights - QQBot now strips model reasoning/thinking scaffolding before native delivery, preventing raw `<thinking>` content from leaking into channel replies. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - MCP tool results now coerce `resource_link`, `resource`, `audio`, malformed image, and future non-text/image blocks at the materialize boundary, preventing Anthropic 400s and poisoned session history after a tool returns richer MCP content. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic extended-thinking sessions recover after prompt-cache expiry or Gateway restart because stream start events wait for `message_start`, letting pre-generation signature errors trigger the existing recovery retry. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697)) Thanks [@openperf](https://github.com/openperf). - Parallel is now a bundled `web_search` provider with `PARALLEL_API_KEY` discovery, guarded endpoint handling, cache-safe session ids, onboarding picker support, and docs. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Google Vertex ADC users get static catalog rows and runtime model resolution again, while single-provider cooldown recovery and memory adapter status checks are more reliable. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90816](openclaw/openclaw#90816)) Thanks [@849261680](https://github.com/849261680). - Matrix can preflight voice notes before mention gating, preserve thread reads/replies through Matrix relations pagination, and carry QA coverage for voice and thread flows. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Auth and plugin install state is more durable: auth profiles now live in SQLite, official npm plugin install records keep their trusted pins, and prerelease fallback integrity checks avoid carrying stale integrity forward. ([#89102](openclaw/openclaw#89102), [#88585](openclaw/openclaw#88585)) - macOS node mode no longer silently self-reconnects away from a healthy direct Gateway session, reducing unexpected companion app session churn. ([#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@vrurg](https://github.com/vrurg). - Upgrade and service paths are safer: cron legacy JSON stores migrate during doctor preflight, service env placeholders no longer mask state-dir secrets, WhatsApp startup waits are bounded, and disabled WhatsApp accounts tear down on config reload. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488), [#90486](openclaw/openclaw#90486), [#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT), [@sallyom](https://github.com/sallyom), [@mcaxtr](https://github.com/mcaxtr), and [@MukundaKatta](https://github.com/MukundaKatta). ##### Changes - Search/providers: add the Parallel bundled web-search plugin, live provider tests, registration contracts, onboarding/docs wiring, and guarded `api.parallel.ai/v1/search` support. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Matrix/channels: add voice-message preflight and thread-aware read/reply behavior, including Matrix QA scenario wiring and docs for voice-message behavior. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Skills/ClawHub: install ClawHub skills backed by GitHub repositories through the resolved install API, download the pinned GitHub commit, keep install-policy checks, and report install telemetry after success. ([#90478](openclaw/openclaw#90478)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - Google Chat/channels: add native approval card actions and click handling so Google Chat approvals use platform-native cards instead of generic message flow. - Mobile: Android provider/model screens now surface expiring, unavailable, unresolved, and attention states more clearly, while iOS settings and Talk tabs keep diagnostics, gateway rows, attachment labels, and unavailable Talk controls reachable. - Memory: QMD search can use the new rerank toggle, and memory adapter status uses the resolved default model identity when checking plain status. ([#61834](openclaw/openclaw#61834)) - Docs/tooling: add Parallel search docs, refresh weather-skill guidance toward `web_fetch`, clarify legacy `openai-codex` auth, document release/test helper scripts, and tighten changed-test routing docs for CI/debugging work. ([#90028](openclaw/openclaw#90028), [#90250](openclaw/openclaw#90250)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Release/process: switch release trains to `YYYY.M.PATCH` monthly patch numbering, keep pre-transition tags compatible, and pin the June 2026 floor at `2026.6.5` after the published beta. - Platform maintenance: refresh Android, Swift/macOS, Docker, CodeQL, Buildx, Docker build/push, and Codex Action dependencies for this release train. ([#74980](openclaw/openclaw#74980), [#81757](openclaw/openclaw#81757), [#86481](openclaw/openclaw#86481), [#86483](openclaw/openclaw#86483), [#90601](openclaw/openclaw#90601)) - QQBot: add `/bot-group-allways on|off` slash command (with named-account and default-account support) to toggle whether group messages require an `@mention` before the bot replies, and clear the runtime config snapshot after the write so the new account-level `defaultRequireMention` takes effect immediately without restart. ([#91423](openclaw/openclaw#91423)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh). ##### Fixes - Channel content boundaries: QQBot now strips reasoning/thinking tags before sending, preserving final answers while hiding internal model narration from users. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - Agents/MCP/providers: coerce non-text/image MCP tool-result blocks before they reach provider converters, preserving valid images and turning richer MCP content into text instead of malformed image blocks. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic/Codex/ACP/agent recovery: defer Anthropic stream start events until `message_start`, strip stale compaction thinking signatures before Anthropic replay, detect unsigned thinking-only stalls, refresh prompt fences after compaction writes, reject empty completion handoffs, preserve parent streaming-off overrides/shared progress commentary, forward heartbeat metadata to context-engine hooks, and cover Codex session/thread migration edge cases. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697), [#90163](openclaw/openclaw#90163), [#90108](openclaw/openclaw#90108), [#89874](openclaw/openclaw#89874), [#89505](openclaw/openclaw#89505), [#90632](openclaw/openclaw#90632), [#89302](openclaw/openclaw#89302), [#90729](openclaw/openclaw#90729), [#90317](openclaw/openclaw#90317), [#90319](openclaw/openclaw#90319)) Thanks [@openperf](https://github.com/openperf), [@100yenadmin](https://github.com/100yenadmin), and [@ooiuuii](https://github.com/ooiuuii). - Provider/model resolution: preserve Google Vertex ADC auth markers in generated catalogs, re-probe a single-provider primary after cooldown, share Codex model visibility, fail closed for unknown model auth, preserve Codex alias availability, keep unresolved profile refs unknown, and avoid resolving auth while listing models. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90702](openclaw/openclaw#90702)) Thanks [@849261680](https://github.com/849261680). - Gateway/macOS/mobile: avoid duplicate Gateway probe warnings by identity, rate-limit node pairing requests while preserving paired-node reconnects, keep macOS node mode on a healthy direct Gateway session, keep iOS diagnostics and gateway rows reachable, and avoid Linux ARM Gradle resource tasks during Android builds. ([#85791](openclaw/openclaw#85791), [#90147](openclaw/openclaw#90147), [#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@giodl73-repo](https://github.com/giodl73-repo) and [@vrurg](https://github.com/vrurg). - TUI/chat/Workboard/auto-reply: optimistic user messages stay stable across stale history reloads, runId reassignment, and abort windows instead of disappearing, jumping, or lingering as ghost rows; Workboard stale lifecycle bulk updates no longer overwrite newer status/provenance; message-tool sends now count as delivery. ([#86205](openclaw/openclaw#86205), [#89600](openclaw/openclaw#89600), [#88592](openclaw/openclaw#88592), [#90123](openclaw/openclaw#90123)) Thanks [@RomneyDa](https://github.com/RomneyDa). - Cron/update/service env: doctor config preflight now migrates legacy cron JSON stores into SQLite before runtime reads, service env planning skips unresolved placeholders that would mask state-dir `.env` values, and session transcript rewrites keep registry markers/discriminants consistent. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT) and [@sallyom](https://github.com/sallyom). - Security/config/tooling: guard MCP HTTP redirects, protect global agent config defaults, and keep release/test/tooling proof failures bounded and explicit. ([#89732](openclaw/openclaw#89732), [#90145](openclaw/openclaw#90145)) - Channels: WhatsApp restarts when per-account config changes, bounds background startup waits, closes failed sockets, and preserves reconnect behavior; Mattermost slash commands keep their state on `globalThis`; Feishu streaming cards preserve full merged content; voice-call tracks Twilio streams after connect; ClickClack reply tools respect `toolsAllow`. ([#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965), [#90486](openclaw/openclaw#90486), [#68113](openclaw/openclaw#68113), [#90534](openclaw/openclaw#90534), [#90181](openclaw/openclaw#90181), [#90607](openclaw/openclaw#90607), [#89500](openclaw/openclaw#89500)) Thanks [@MukundaKatta](https://github.com/MukundaKatta), [@mcaxtr](https://github.com/mcaxtr), [@infoanton](https://github.com/infoanton), [@mushuiyu886](https://github.com/mushuiyu886), and [@sahibzada-allahyar](https://github.com/sahibzada-allahyar). - Feishu: retry transient send rate-limit errors (HTTP 429, per-chat code 230020, tenant-level code 11232) with linear backoff, including SDK responses that fulfill with rate-limit bodies instead of throwing, and route streaming-card sends through the retry wrapper. ([#89659](openclaw/openclaw#89659)) Thanks [@ladygege](https://github.com/ladygege). - Release/CI/E2E: main CI guard drift, PR merge diff scoping, live Docker credential staging, base-image qualification, installer Docker classification, Playwright dependency install recovery, API-key auth for Codex live Docker lanes, Parallels option terminators, and JSON-mode progress handling are tighter so release proof fails cleaner. ([#90532](openclaw/openclaw#90532), [#90287](openclaw/openclaw#90287), [#90058](openclaw/openclaw#90058)) Thanks [@RomneyDa](https://github.com/RomneyDa), [@hxy91819](https://github.com/hxy91819), and [@mrunalp](https://github.com/mrunalp). - Release/CI/E2E: Docker E2E and live Docker harness runs now apply default memory, CPU, and process ceilings while preserving explicit per-lane overrides. - Release/CI/E2E: plugin lifecycle matrix resource sampling now fails phases that exceed RSS, wall-clock, or CPU ceilings instead of only logging the measurements. - Release/CI/E2E: Codex npm plugin live assertions now cap transcript discovery and diagnostic log reads so failure proof stays bounded. - Tests/state isolation: QA Lab valid-tool-call metrics now require runtime tool-call evidence when runtime parity data is available instead of counting tool-backed scenario pass status alone. - Tests/state isolation: QA Lab runtime parity now fails planned-only tool-call rows without matching tool results instead of treating matching mock plans as real tool evidence. - Tests/state isolation: provider, media, auth, cron, task, session, sandbox, Gateway, and Codex timeout fixtures now scope more home/state/env data per test, reducing cross-test leakage and making release validation failures less noisy. ([#90027](openclaw/openclaw#90027), [#89974](openclaw/openclaw#89974)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/963

openclaw-barnacle Bot added cli CLI command changes commands Command implementations size: M triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels Jun 4, 2026

MonkeyLeeT changed the title ~~[codex] fix cron legacy migration~~ fix(cron): auto-migrate legacy cron store Jun 4, 2026

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels Jun 4, 2026

MonkeyLeeT marked this pull request as ready for review June 4, 2026 15:56

MonkeyLeeT force-pushed the codex/fix-cron-legacy-migration branch from 2bee816 to 9c995f3 Compare June 4, 2026 15:59

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 4, 2026

MonkeyLeeT added 2 commits June 4, 2026 09:01

fix(cron): auto-migrate legacy cron store

e5defe8

fix(cli): run gateway fast-path bootstrap

216ca15

MonkeyLeeT force-pushed the codex/fix-cron-legacy-migration branch from 9c995f3 to 216ca15 Compare June 4, 2026 16:02

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 4, 2026

refactor(cron): share legacy migration repair

bd861ff

openclaw-barnacle Bot removed cli CLI command changes proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 4, 2026

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 4, 2026

refactor(cron): remove auto migration wrapper

ee962f7

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 4, 2026

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 4, 2026

jalehman self-assigned this Jun 5, 2026

Merge branch 'main' into codex/fix-cron-legacy-migration

f5aa1b6

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 5, 2026

clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. merge-risk: 🚨 message-delivery 🚨 May drop, duplicate, misroute, suppress, or wrongly target messages. labels Jun 5, 2026

jalehman merged commit 21aa297 into openclaw:main Jun 5, 2026
177 of 179 checks passed

github-actions Bot mentioned this pull request Jun 5, 2026

📡 Upstream Digest — 2026-06-05 17:48 UTC curtismercier/openclaw-mods#1020

Open

MonkeyLeeT deleted the codex/fix-cron-legacy-migration branch June 5, 2026 20:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(cron): auto-migrate legacy cron store#90208

fix(cron): auto-migrate legacy cron store#90208
jalehman merged 5 commits into
openclaw:mainfrom
MonkeyLeeT:codex/fix-cron-legacy-migration

MonkeyLeeT commented Jun 4, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

MonkeyLeeT commented Jun 4, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

Uh oh!

jalehman commented Jun 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

MonkeyLeeT commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Root Cause

Verification

Real behavior proof

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

MonkeyLeeT commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

jalehman commented Jun 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

MonkeyLeeT commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

MonkeyLeeT commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading