Upgrade default OpenClaw to 2026.10.2

[Angnuo (angnuoli)]

Description

Upgrade the current main baseline from OpenClaw 2026.9.3 to stable 2026.10.2, preserving the newer Windows Node/MXC sandbox and local-model features.

Merged upstream main (6de7bbf) with a normal merge commit; no history was rewritten. The PR remains a draft because full live installation/model/WeChat verification is outstanding and the upstream baseline has unrelated test/lint/format failures.

Upstream release: https://github.com/openclaw/openclaw/releases/tag/v2026.10.2

Related Issue

N/A

Changes

• Pin the default installer and legacy dependency helper to OpenClaw 2026.10.2.
• Preserve upstream's recommended Node 26 line, 26.1.0 fallback, shared PowerShell runtime gate, and supported engine range >=24.16.0 <25 || >=26.1.0.
• Preserve existing Node directories and their ownership during upgrade rollback, including restored OpenClaw packages sharing the npm prefix.
• Re-pin the Windows Node/MXC approval preload to the real 10.2 published modules and SHA-256 values. Follow the moved plan normalizer and combined approval branch; await asynchronous one-use consumption before minting a proof. Keep operator-only, one-use, exact-source and exact-hash checks fail-closed.
• Allow the verified 10.2 Gateway in local/default/session model selection while retaining the separate existing provider-version checks and the pinned 9.3 llama.cpp provider artifact.
• Preserve upstream's removal of automatic Weixin bundling/installation. The optional maintained Weixin source still receives the 10.2 SDK migration and standalone staging tests; it is not reintroduced into build.ps1 or the installer.
• Update bilingual documentation and regression tests to match the combined behavior.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• CI/CD or build configuration change
• Refactoring (no functional changes)

Testing

• Tests pass locally (cd desktop && npm run test)
• Renderer tests pass locally (cd desktop/renderer && npm run test)
• Build succeeds (cd desktop && npm run build)
• Manual testing performed (describe below)

Results after merging the latest upstream baseline:

• python -m unittest discover -s tests -q: passed, 294 tests.
• npm exec -- vitest run src\openclaw-approval-replay-compat.test.ts src\local-model-service.test.ts src\default-model-selection.test.ts src\session-model-service.test.ts (in desktop, with MICROCLAW_OPENCLAW_TEST_PACKAGE_DIR set): passed, 191 tests, including published approval-module hash/patch-point validation, patched-module syntax checks, real preload initialization, asynchronous consume-denial checks, and model-selection coverage on both 9.3 and 10.2.
• npm exec -- vitest run src\path-resolver.test.ts src\gateway-manager.test.ts (in desktop): passed, 62 tests.
• npm exec -- tsc --noEmit (in desktop): passed.
• npm test (repository root): failed on one existing upstream desktop test. The 5 optional Weixin staging tests passed; desktop Vitest reported 1,371 passed, 11 skipped and 1 failed. desktop/src/startup-order.test.ts:18 searches for the old startGateway().catch spelling in main.ts. Both files are unchanged relative to upstream 6de7bbf. The root command stopped before renderer tests, which were then run separately.
• Set-Location desktop\renderer; npm test: passed, 471 tests.
• Set-Location desktop; npm run build: passed, with Vite's large-chunk warning.
• python -m ruff check deployer\config.py deployer\openclaw_version.py deployer\windows_setup.py tests\test_openclaw_version.py tests\test_runtime_gates.py tests\test_windows_setup_upgrade.py: passed.
• npm run lint: failed on two existing errors in untouched upstream files — desktop/src/chat-attachments.ts:105 (no-control-regex) and desktop/src/openclaw-upgrade-recovery.ts:236 (unused readJsonObject); 116 warnings were also reported.
• npm run format:check: failed on 13 untouched upstream files. The files modified for conflict resolution were formatted separately. Unrelated formatting was not mixed into this merge.
• git diff --cached --check: passed before the merge commit.

The three 10.2 approval modules were downloaded from the published UNPKG package and compared byte-for-byte against its SHA-256 SRI metadata. A scratch package directory contained the published package.json and the specific runtime files needed for preload validation; it was not a full runnable Gateway installation. The pinned local-provider SDK imports were also checked against the 10.2 host's public exports.

Full build.ps1 installer/native-helper packaging, live Gateway/Windows Node/MXC command execution, model downloads and WeChat QR/message flows were not run. Direct npm registry downloads remain affected by this environment's 404/TLS failures. No existing local installation or user state was modified. The optional Weixin tests use narrow SDK test doubles and are not WeChat E2E coverage.

Checklist

• My code follows the coding guidelines of this project
• I have performed a self-review of my code
• I have commented my code where necessary
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or my feature works
• New and existing unit tests pass locally with my changes