Fix OpenClaw 10.2 installation and unify live model selection

[Suzhen Zheng (benniao85)]

Description

Fix OpenClaw 2026.10.2 installation compatibility and unify model configuration and selection across MicroClaw. Provider forms, default-model selection, and conversation-model selection share authenticated live catalogs instead of mixing static presets with saved-model subsets. Model-only changes no longer unconditionally restart the Gateway.

Includes the earlier installation fixes and is merged with main at f605761, retaining both model-startup assertions and upstream MXC lifecycle guards.

Related Issue

Related to #101 (closed): addresses remaining hardcoded model-list behavior and consistency across the three model selectors, rather than expanding the provider-family menu.

Changes

• Support OpenClaw 10.2 SQLite workers and captured local-model provider modules while retaining pinned identity/source checks and scoped sandbox access.
• Pin the compatible search plugin, preserve quoted Node paths, validate actual sandbox access, and avoid unnecessary database migration during same-version updates.
• Share bounded, authenticated, read-only provider discovery across all three model selectors. Isolate draft credentials and surface discovery errors without static fallback lists.
• Register newly selected models with revision-guarded Gateway updates and verify application before switching, preserving credentials, policies, defaults and conversation overrides.
• Keep known non-chat model families visible but disabled with explanations and enforce restrictions in the main process. Distinguish access rejection from invalid credentials and incompatible requests.
• Simplify provider cards with chevrons, adjacent API-key/refresh actions, key-before-model field order, no duplicate saved-model rows or headings, and independently persisted form selections.
• Use standard button activation and accessible, named real Element Plus popovers. Add opt-in non-activating startup/update behavior and distinguish installer captions from the desktop.
• Add regression and opt-in real-provider E2E tests and update English/Chinese documentation.

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)

Validation after merging main:

Command	Result
cd desktop; npm test -- --reporter=dot	Passed: 1,614 Vitest tests; 14 environment-dependent skips; 5 WeChat staging tests passed
cd desktop\renderer; npm run test -- --reporter=dot	Passed: 535 tests
cd desktop; npm run build	Passed: TypeScript, Vue type checks and Vite build
python -m unittest discover -s tests -p test_windows_setup_upgrade.py -q	Passed: 132 tests; files unchanged by the main merge
python -m unittest discover -s tests -p test_webview_bridge.py -q	Passed: 37 tests; files unchanged by the main merge
git diff --check / git diff --cached --check	Passed

Existing Vite large-chunk warnings and renderer shallow-stub warnings remain.

Additional feature-build validation on 0e89412, before merging main:

• powershell -ExecutionPolicy Bypass -File .\build.ps1 — passed; generated desktop, portable ZIP, installer ZIP and full Setup EXE.
• cd desktop; npx vitest run src\provider-model-registration.integration.test.ts --reporter=verbose, with MICROCLAW_TEST_OPENCLAW_ENTRY set — passed against isolated OpenClaw 10.2; no inference or Gateway restart during registration/selection.
• cd desktop; npx vitest run src\provider-model-live.integration.test.ts --reporter=verbose, with MICROCLAW_TEST_OPENCLAW_ENTRY and MICROCLAW_TEST_LIVE_QWEN_CONFIG explicitly set — passed with real Qwen Max/Flash replies, preserved default/session scope, unchanged source configuration and no restart. This optional test may consume quota and is skipped by default.
• Real Windows transactional installation committed; installed archive matched the package; HTTP health and authenticated configuration RPC checks passed.
• Actual installed-client E2E covered matching 176-ID catalogs, Max/Flash replies, access-denied recovery, incompatible-model rejection, credential gating, refresh states, model-only Save, reopening and persistence across restart.
• Verified default changes preserve existing session overrides; restored original default/form preferences, retained AppContainer, and did not change billing settings.
• Verified one desktop main process, non-activating update/startup and cleanup of debugging listeners. Final background verification used app-local actions without keyboard/mouse takeover.

These checks do not certify every returned model's account entitlement or all input/tool capabilities. MiniMax inference was not exercised without an authorized MiniMax credential. Local installer artifacts are unsigned.

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

[microsoft-github-policy-service]

Suzhen Zheng (@benniao85) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.