chore(deps): update OpenClaw to 2026.9.5

[nvidia-nemopatch-writer]

Outcome

Updates managed OpenClaw and its official channel/search plugins from 2026.9.2 to 2026.9.5 while preserving NemoClaw's proxy, device authorization, private-state, and tool compatibility behavior.

Reason

OpenClaw 2026.9.5 changes distributed modules to .mjs, embeds separate worker implementations, changes native patch targets, and changes the package graphs used by offline plugin installation. Version-pin changes alone do not preserve those integrations.

Changes

• Rebuild runtime and messaging locks with current security overrides and verified archive identities. Preserve the prerequisite trust policy from chore(deps): trust OpenClaw 2026.9.5 manifests #12380; remove obsolete unselected archive entries.

• Adapt exact patch targets for .mjs, the npm 12 parser facade, trimmed device request IDs, private state modes, nested tool input, and MCP npx arguments.

• Patch the separately bundled worker with drift checks and descriptor-bound writes. Require the worker to exist; cover symlink and replacement-path rejection, idempotence, and actual worker behavior.

• Isolate WeChat and official-channel disposable npm caches. Retain resolved lock graphs while seeding metadata for fresh offline installs and supplying the pinned host-override archives.

• Update the remote-dashboard guard's exact reviewed messaging-install instruction digest, retaining rejection of appended configuration rewrites. Supply the required worker in synthetic Dockerfile patch fixtures while preserving their package metadata.

• Admit reviewed pairing database schemas 15 and 17 while preserving descriptor, identity, credential, and scope checks. Read native token rotation and rollback through the shipped adapter in the real-distribution proof. Explicitly enable the existing NemoClaw prompt-context hook under the new upstream permission policy.

• Load the native post-upgrade schema repair and migration-lease checks from both .js and .mjs modules. Find canonical migration SQL in its reviewed state-module family while retaining ambiguity rejection. Exercise both fixture layouts and the actual pinned package after native credential creation.

• Retire only the global gateway-owner lease from the private SQLite archive copy. This lets a replacement container start without inheriting the retired container’s unexpired lease; the live database and other leases remain unchanged. Fail closed on an unrecognized schema.

• Keep the native CLI launcher inside the reviewed OpenClaw package so 2026.9.5 self-update preview recognizes its ownership. Preserve the wrapper’s arguments and npm-prefix behavior.

• Preserve main’s Tavily union validator and check the installed 2026.9.5 plugin. Keep the historical Slack remediation test independent of the new production version pins.

• Create synthetic worker fixtures exclusively and update their package manifests through one file descriptor, resolving the two CodeQL race findings.

• Split archive download stages within image-layer limits, bound the verified larger OpenClaw archive, and update image metadata and current user guidance.

• Start the pairing watcher only after the native gateway startup probe succeeds. This prevents its CLI preflight from competing with gateway schema migration for the shared state lock. Keep the captured process identity, a bounded wait, and the existing approval policy.

• Repair 9.5 startup and lifecycle handling: remove only empty, owned legacy state files; wait for confirmed gateway readiness, including custom-image onboarding; retain descriptor and file-identity protections.

• Support the reviewed 9.5 QR renderer and Slack .mjs modules. Keep denied-sender behavior and private feedback intact.

• Make lifecycle E2E establish the required native admin approval, retain the sandbox namespace, assert plugin-install success, and fail immediately when restore prerequisites are missing. Preserve all existing assertions.

• Integrate main's selected-channel offline-cache repair and update the exact Dockerfile instruction digest accepted by the dashboard guard.

• Reserve native gateway startup time before the host declares canonical pairing absent. Both ordinary and Portable settlement allow the existing 330-second startup bound plus the existing 60-second device-list window; canonical device identity and scopes still determine success.

• Restore the previously approved budget paragraph lost during the JSON conflict resolution. Exception entries, hashes and enforcement remain unchanged.

• Preserve native startup failures in the existing managed gateway log and private watcher status. Ordinary and Portable onboarding now distinguish a gateway timeout or exit from a pairing failure and point to the durable diagnostic and recovery action. Existing startup bounds, device identity and approval scope remain unchanged.

Verification

• Current candidate: 52a0fb1b8e25c3317f5ae62819b4f53420e7d908, including merged SDK prerequisite fix(e2e): install the locked SDK from reviewed archive bundles #12765 and canonical validation updates from fix(test): preserve coverage across native and Vitest loaders #12713.
• The recovery-message regression produced four expected failures before the correction. All 89 focused ordinary and Portable pairing tests pass afterward. Both startup-timeout and gateway-exited messages retain the persistent-log path and identify nemoclaw <sandbox> gateway restart.
• Local CLI build, typecheck, lint, formatting, all 13 selected repository checks, normal commit hooks and the full normal pre-push gate passed. Genuine matching Pi inputs were verified; no hook or receipt exception was used.
• Current core CI passed: 23 successful jobs and two expected skips. Podman CPU checks also passed.
• Current Portable qualification passed all 13 phases. Authenticated artifact 11522904555 verifies rootless Podman lifecycle, restored authenticated health and forwarding, and stopped-state observations. This is Portable qualification; it does not establish a full OpenClaw 2026.9.5 E2E pass.
• All nine PR Advisor specialists are clear for this exact candidate. Their authenticated findings, summaries and E2E reports were read in full: no blocking findings and no unresolved additional E2E recommendations.
• Both current Pi architecture jobs passed in managed-image run 37714665888. Genuine AMD64 artifact 11523746225 and ARM64 artifact 11523403576 match this candidate and their immutable published digests. Their exact receipt bytes and archive digests were verified.
• Genuine current audit artifact 11522954535 reports zero high/critical and three moderate findings for runtime lock SHA-256 b73ebd8bb5e15cfcf080a21beaca0dce50cbca903988b20be74d49c9498baeb7. Its manifest, lock, raw response and exception-policy hashes were verified. The receipt expires at 2026-10-08T13:49:29.542Z.
• Current managed-image publication and activation passed. Docker artifact 11524613492 and rootless Podman artifact 11525432080 each record 28 agent turns, all 13 phases and all 13 cleanup actions passing for this candidate. Their archive digests, source revision, cohort and summaries were verified. OpenClaw and Hermes external-image onboarding, drift rejection, rebuild and retained-image checks also passed. Podman 5.7 ran rootless with Docker unavailable and zero guarded Docker invocations.
• Complete feedback collection found 81 terminal checks: 58 passed, 21 skipped, and two growth-guardrail failures for the same approved budget transition described below. All paginated comments, reviews and threads were inspected; all three existing review threads are resolved. There are no new candidate-owned findings.
• The exact approved chore(deps): update OpenClaw to 2026.9.5 #12382 budget transition, its approval paragraph and main's fix(onboard): check selection drift before fresh sandbox reuse #12769 entry remain unchanged.
• Full trusted E2E qualification remains outstanding. The diff contains no secrets, API keys, or credentials.

Review notes

The previous Advisor P1 is resolved. Both OpenClaw onboarding paths now identify the supported gateway restart command after native startup fails, retain the persistent-log path, and instruct the operator to resume onboarding after a successful restart. The current nine specialist reports confirm no blocking findings.

The independent growth check still requires the exact approved budget transition in #12718 to be adopted by trusted main. Candidate policy cannot waive that check. #12718's current CI failed during transitive npm resolution and still needs fresh Advisor clearance. Trusted main also needs the trust policy from #12380 for full 2026.9.5 qualification. The shared E2E controller history lookup was repaired by merged #12790; #12789 was closed as superseded.

Self-review covered the public restart command, both settlement callers, the four failing regression cases followed by 89 passing tests, unchanged Pi receipt inputs, and preservation of the approved budget. This PR remains a draft pending the remaining checks and full E2E evidence. CodeRabbit is deferred at the user's direction; no merge is authorized.

---

Signed-off-by: Prekshi Vyas prekshiv@nvidia.com

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: NVIDIA/NemoClaw/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8a313dd3-bead-4047-a54e-8c796033c925

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-code-quality]

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall line coverage in commit 52a0fb1 in the nemopatch/openclaw-u... branch is 97%. The line coverage in commit 63002cd in the main branch is 96%.

Show a line coverage summary of the most impacted files.

File	main 63002cd	nemopatch/openclaw-u... 52a0fb1	+/-
nemoclaw/src/onboard/config.ts	98%	96%	-2%
nemoclaw/src/index.ts	94%	93%	-1%
nemoclaw/src/bl...print/runner.ts	95%	95%	0%
nemoclaw/src/bl...ime-identity.ts	97%	97%	0%
nemoclaw/src/bl...t-management.ts	100%	100%	0%
nemoclaw/src/co.../config-show.ts	100%	100%	0%
nemoclaw/src/commands/slash.ts	100%	100%	0%
nemoclaw/src/on...native-route.ts	0%	100%	+100%

TypeScript / code-coverage/cli

The overall line coverage in commit 52a0fb1 in the nemopatch/openclaw-u... branch is 86%. The line coverage in commit 63002cd in the main branch is 84%.

Show a line coverage summary of the most impacted files.

File	main 63002cd	nemopatch/openclaw-u... 52a0fb1	+/-
src/lib/onboard.ts	62%	46%	-16%
src/lib/onboard...rchestration.ts	41%	32%	-9%
src/lib/state/sandbox.ts	92%	84%	-8%
src/lib/inferen...file/cleanup.ts	73%	88%	+15%
src/lib/actions...ess-recovery.ts	65%	81%	+16%
src/lib/state/l...diness-lease.ts	66%	82%	+16%
src/lib/inferen...ollama/proxy.ts	41%	61%	+20%
src/lib/onboard.../application.ts	55%	84%	+29%
src/lib/inferen...nvidia/index.ts	0%	84%	+84%
src/lib/onboard...ternal-image.ts	0%	91%	+91%

---

_{Updated October 08, 2026 02:06 UTC}

[prekshivyas]

@coderabbitai review

[prekshivyas]

@coderabbitai review

[prekshivyas]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review skipped.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[github-actions]

PR Review Advisor finished for commit 52a0fb1. Include the Advisor findings in the complete PR feedback collection. Verify and group valid findings before repair.

Request review only when Require no Advisor blockers is green.

All previous runs