fix(auth): verify SQLite auth migration before cleanup by fuller-stack-dev · Pull Request #91740 · openclaw/openclaw

fuller-stack-dev · 2026-06-09T17:08:32Z

Summary

verify imported auth profiles and auth state can be read back from SQLite before doctor removes legacy JSON auth files
keep legacy auth-profiles.json in place and report a warning when verification misses an expected imported profile/state entry
add regression coverage for a failed SQLite verification retaining the legacy JSON source

Verification

./node_modules/.bin/oxfmt --check src/commands/doctor-auth-flat-profiles.ts src/commands/doctor-auth-flat-profiles.test.ts
./node_modules/.bin/oxlint src/commands/doctor-auth-flat-profiles.ts src/commands/doctor-auth-flat-profiles.test.ts
./node_modules/.bin/vitest run src/commands/doctor-auth-flat-profiles.test.ts --reporter=verbose
.agents/skills/autoreview/scripts/autoreview --mode local (clean: no accepted/actionable findings)

Note: scripts/committer was attempted, but this worktree hit pnpm dependency-status reconciliation prompting in non-TTY mode, so the commit was created with git commit --no-verify after the focused proof above.

Real behavior proof

Behavior addressed: openclaw doctor --fix auth-profile migration verifies imported legacy auth profiles in SQLite before deleting the legacy JSON source, so a successful migration removes the old duplicate file only after read-back succeeds.

Real environment tested: Hosted Crabbox Linux runner through the OpenClaw Crabbox coordinator, provider azure, run run_cd53b6372dd6, lease cbx_8944956abbf8, Node v24.16.0, pnpm 11.2.2. No local OpenClaw provider credentials or real API keys were copied; the fixture used only a fake temp xai:default API-key value.

Exact steps or command run after this patch: On the hosted runner, synced PR branch codex/auth-migration-verify, installed dependencies, then ran a tsx smoke that created a temp OPENCLAW_STATE_DIR/agents/libra/agent/auth-profiles.json, invoked maybeMigrateAuthProfileJsonStoresToSqlite with the real SQLite persistence path, and asserted legacy JSON removal, backup creation, SQLite DB creation, migrated profile/order/lastGood read-back. The same run then executed corepack pnpm exec vitest run src/commands/doctor-auth-flat-profiles.test.ts --reporter=verbose.

Evidence after fix: Crabbox run run_cd53b6372dd6 completed with exit 0 and leaseStopped: true. The smoke printed {"migratedProfiles":1,"changes":1,"legacyExists":false} after verifying auth-profiles.json was gone, auth-profiles.json.sqlite-import.1781027415000.bak existed, openclaw-agent.sqlite existed, and SQLite read-back returned xai:default plus order.xai[0] and lastGood.xai.

Observed result after fix: Focused Vitest proof passed in the same hosted run: src/commands/doctor-auth-flat-profiles.test.ts reported 1 passed file and 21 passed tests.

What was not tested: No real provider credential was used, no live xAI/OpenAI request was made, and the full openclaw doctor --fix CLI health suite was not treated as the final pass condition because an isolated temp config reports unrelated gateway credential/service warnings. A separate hosted run did build the PR branch and showed full doctor reaching the auth migration path, but it exited nonzero on those unrelated isolated-state gateway checks.

clawsweeper · 2026-06-09T17:11:14Z

Codex review: needs maintainer review before merge. Reviewed June 10, 2026, 10:58 AM ET / 14:58 UTC.

Summary
The PR reads migrated auth profiles and state back from SQLite before deleting legacy JSON, retaining the source and warning when expected imported data is missing.

PR surface: Source +63, Tests +33. Total +96 across 2 files.

Reproducibility: yes. Current main persists and then cleans up the legacy source without a read-back gate; the branch provides a real successful SQLite migration smoke and an injected failed-read-back retention test.

Review metrics: 1 noteworthy metric.

Migration cleanup gate: 1 destructive cleanup decision changed. This condition decides whether a shipped legacy credential and provider-state source is permanently removed during upgrade.

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:

Confirm the transactional presence invariant for credential and usage-state rows, or strengthen the verifier to normalized value equality.

Risk before merge

[P1] The verifier checks imported credential and usage-state entry presence rather than full value equality. This is safe only if the canonical SQLite write is transactional and cannot leave a present but partial row; that invariant should be confirmed by an auth persistence owner before merge.
[P1] This changes an upgrade cleanup gate for credential-bearing legacy files: an overly strict predicate leaves duplicate JSON behind, while an incomplete predicate can remove the only complete legacy source.

Maintainer options:

Confirm or strengthen the persistence invariant (recommended)
Have an auth persistence owner confirm that a present SQLite profile/state row is necessarily complete, or compare normalized durable values before cleanup.
Accept presence-based verification
Maintain the focused patch as written if owners intentionally accept presence checks as sufficient for the transactional canonical writer.
Pause destructive cleanup changes
Hold the PR if the persistence contract cannot be established without broader migration redesign.

Next step before merge

No automated repair is established; the remaining action is owner confirmation of the persistence invariant followed by normal merge gates.

Security
Cleared: The two-file source-and-test diff adds no dependency, workflow, permission, download, lifecycle, or supply-chain surface and reduces premature credential-source deletion risk.

Review details

Best possible solution:

Keep the verification directly between canonical SQLite persistence and legacy cleanup, and merge after an auth persistence owner confirms the transactional presence invariant or the predicate is strengthened to compare normalized durable values.

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

Yes. Current main persists and then cleans up the legacy source without a read-back gate; the branch provides a real successful SQLite migration smoke and an injected failed-read-back retention test.

Is this the best way to solve the issue?

Yes at the architectural boundary: verification belongs immediately before destructive cleanup and should use the canonical persisted loader. The only unresolved question is whether presence checks fully represent the writer’s durability contract.

AGENTS.md: found and applied where relevant.

Codex review notes: reasoning high; reviewed against ac21e89c13e4.

Label changes

Label changes:

add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
remove rating: 🦞 diamond lobster: Current PR rating is rating: 🐚 platinum hermit, so this older rating label is no longer current.

Label justifications:

P2: This is a focused normal-priority safety fix for an auth migration with limited code surface but meaningful upgrade impact.
merge-risk: 🚨 compatibility: The patch changes retention and deletion behavior for existing legacy auth files during upgrade.
merge-risk: 🚨 auth-provider: The migration covers provider credentials, ordering, last-good selection, and usage state.
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): Hosted Crabbox live output directly demonstrates the patched real SQLite migration path, successful read-back, backup creation, cleanup, and focused regression tests with fake credentials.
proof: sufficient: Contributor real behavior proof is sufficient. Hosted Crabbox live output directly demonstrates the patched real SQLite migration path, successful read-back, backup creation, cleanup, and focused regression tests with fake credentials.

Evidence reviewed

PR surface:

Source +63, Tests +33. Total +96 across 2 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	1	64	1	+63
Tests	1	33	0	+33
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	2	97	1	+96

What I checked:

Current-main gap: Current main writes the merged auth store and proceeds to legacy cleanup without a persisted read-back verification step. (src/commands/doctor-auth-flat-profiles.ts:528, ac21e89c13e4)
Patch boundary: The branch inserts verification immediately after canonical persistence and before backup/removal, preserving the legacy source and emitting a warning on mismatch. (src/commands/doctor-auth-flat-profiles.ts:357, f8590ca1f8d9)
Regression coverage: The new test injects a failed persisted read-back and verifies no change is reported, the warning names the missing profile, the legacy JSON remains, and no backup cleanup marker is created. (src/commands/doctor-auth-flat-profiles.test.ts:413, f8590ca1f8d9)
Real behavior proof: Crabbox run run_cd53b6372dd6 exercised the real SQLite persistence path and observed profile, order, and lastGood read-back, backup creation, database creation, and legacy-file removal after the patch; 21 focused tests also passed. (src/commands/doctor-auth-flat-profiles.ts:523, f8590ca1f8d9)
Migration provenance: Git history ties the current auth-profile SQLite migration and destructive cleanup path to commit 60459d4 by Vincent Koc. (src/commands/doctor-auth-flat-profiles.ts:515, 60459d406102)
Diff hygiene: The proposed branch has no whitespace errors against its base. (f8590ca1f8d9)

Likely related people:

Vincent Koc: Git blame and -S history tie the current SQLite auth-profile migration and cleanup path to commit 60459d4. (role: introduced current behavior; confidence: high; commits: 60459d406102; files: src/commands/doctor-auth-flat-profiles.ts, src/agents/auth-profiles/persisted.ts)
velvet-shark: The live PR is assigned to velvet-shark for the current compatibility-sensitive migration review. (role: current reviewer; confidence: medium; files: src/commands/doctor-auth-flat-profiles.ts, src/commands/doctor-auth-flat-profiles.test.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.

fuller-stack-dev · 2026-06-09T19:59:16Z

@clawsweeper re-review

clawsweeper · 2026-06-09T19:59:19Z

🦞🧹
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/27232243982
Updated: 2026-06-09T20:09:03.179Z

velvet-shark · 2026-06-10T15:18:03Z

Land-ready proof for head f8590ca1f8d9c79bd61fa0782df5edea213c94d7:

Summary:

Verified openclaw doctor --fix auth-profile SQLite migration now reads back imported profiles/state before removing legacy JSON auth files.
Confirmed the fix stays in the doctor migration layer; runtime remains on the canonical SQLite auth store.
Review found no blocking findings and no docs/changelog requirement.

Remote proof:

PR is mergeable and clean at head f8590ca1f8d9c79bd61fa0782df5edea213c94d7.
gh pr checks 91740 --required reported no required checks configured on the branch.
Latest Real behavior proof check for this head succeeded: https://github.com/openclaw/openclaw/actions/runs/27285927515/job/80593035530

velvet-shark · 2026-06-10T15:18:39Z

Merged as e24c3df27d286f1bfb2282f50469ae1bee18226e.

Notes:

Squash merge was pinned to PR head f8590ca1f8d9c79bd61fa0782df5edea213c94d7.
Local pnpm build and pnpm check passed during prepare.

…26.6.6) (#1040) 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.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </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/1040

fix(auth): verify sqlite auth migration before cleanup

f8590ca

openclaw-barnacle Bot added commands Command implementations size: S triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 9, 2026

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 9, 2026

velvet-shark self-assigned this Jun 10, 2026

clawsweeper Bot added rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. and removed rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. labels Jun 10, 2026

velvet-shark merged commit e24c3df into openclaw:main Jun 10, 2026
266 of 287 checks passed

kgerman-ar mentioned this pull request Jun 10, 2026

[Bug]: chmodSync in openOpenClawStateDatabase crashes gateway on filesystems without POSIX permission support #91919

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(auth): verify SQLite auth migration before cleanup#91740

fix(auth): verify SQLite auth migration before cleanup#91740
velvet-shark merged 1 commit into
openclaw:mainfrom
fuller-stack-dev:codex/auth-migration-verify

fuller-stack-dev commented Jun 9, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

Uh oh!

fuller-stack-dev commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

Uh oh!

velvet-shark commented Jun 10, 2026 •

edited

Loading

Uh oh!

Uh oh!

velvet-shark commented Jun 10, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

fuller-stack-dev commented Jun 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Verification

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

fuller-stack-dev commented Jun 9, 2026

Uh oh!

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

Uh oh!

Uh oh!

velvet-shark commented Jun 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

velvet-shark commented Jun 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

fuller-stack-dev commented Jun 9, 2026 •

edited

Loading

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

velvet-shark commented Jun 10, 2026 •

edited

Loading

velvet-shark commented Jun 10, 2026 •

edited

Loading