Speed up repeat installs safely

[angnuoli]

Description

Speeds up repeat MicroClaw installations while preserving safe OpenClaw and plugin rollback behavior. The measured same-version install path drops from 308.81s to about 70.72s of active processing time.

Related Issue

N/A

Changes

• Add per-step installer timing with total and slowest-step summaries in both installer UIs.
• Add a same-version OpenClaw fast path backed by a locked managed-state transaction; real upgrades and plugin mutations retain full backup/rollback.
• Reconcile the bundled WeChat plugin through the official OpenClaw CLI, skip matching registered payloads, and preserve user enable/allow/deny policy across retries.
• Bind plugin installation to a Windows kill-on-close Job Object before execution and enforce bounded timeout/whole-tree termination.
• Keep close-app confirmation dialogs visible in the WebView installer.
• Add regression coverage for transactions, plugin registration/policy, retries, process lifetime, timing, and confirmation 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)

Python installer suite: 158 tests passed. Full build.ps1 completed successfully. A same-version installation was manually measured at 167.72s total, including about 97s of user confirmation wait, for about 70.72s of active processing; the WeChat plugin fast path took 1.10s.

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