test(desktop): 收尾 Windows 10/11、WebView2 与 DPI 矩阵

[Qiyuanqiii]

Refs #55
Follow-up blocker: #85

Changes

• harden the Windows desktop matrix with clean candidate provenance, real-window normal-exit checks, and WebView2 ClientState discovery;
• make the desktop shell fit the 1024x768 / 200% (512x384 logical) test surface by using a compact responsive layout and bounded native minimum size;
• fail closed before Wails starts when the installed WebView2 client DLL is missing, malformed, wrong-architecture, or missing its required entry point;
• add sanitized, candidate-bound r4 evidence for Windows 10 at 100/125/200%, Windows 11 at 150%, offline startup, and missing/old/corrupt WebView2 scenarios.

Why / root cause

Issue #55 lacked real Windows release-candidate evidence. The first Win10 pass found two product defects: the native/CSS minimum sizes exceeded the 200% logical viewport, and a malformed WebView2 DLL passed the version-only check before Wails terminated the process without recovery guidance. The evidence collector also queried only legacy Clients keys while the bundled Go loader uses ClientState.

Historical evidence candidate

• version: v0.1.0-issue55-r4
• revision: c3096e52bf1179b295840b2f5f24dd4708849499
• SHA-256: 86791c530996eea604501577287feadb7002296252fa344a96bb406c554934a4
• clean / reproducible: yes (two byte-identical builds)

Historical candidate checks

• go test -count=1 ./... -timeout 20m
• Desktop tagged Go boundary tests
• 59 frontend test files / 241 tests
• TypeScript + Vite production build
• npm audit: 0 vulnerabilities
• reproducible Windows build and compatibility checks
• Win10 100/125/200% and Win11 150% automated matrices: all five scenarios pass
• manual single-monitor 100/200% shell, offline startup, and WebView2 missing/old/corrupt observations: pass

Remaining evidence

The host has one display and the VM connection cannot be safely driven for the full interactive checklist. Mixed-DPI multi-monitor movement and the theme/language/sidebar/long-content/Markdown/Activity/approval/settings sign-off remain explicitly blocked/not_run in the manifest and are tracked by #85. This PR does not claim Windows release readiness or close #55.

Review corrections (2026-08-18)

• merged the current main branch and resolved the release-script conflict, so the PR is mergeable again;
• changed WebView2 integrity inspection to parse the on-disk PE export table without loading or executing the candidate DLL;
• aligned matrix runtime discovery with all Stable/Beta/Dev/Canary ClientState channels before the documented Clients fallback;
• limited matrix cleanup to process IDs started by that exact run, preventing termination of a pre-existing user instance;
• added a compact 512x384 logical-viewport sidebar rule and verified Workbench/Settings in a real browser with zero console errors;
• added a conditional test against the host's actually installed WebView2 Runtime.

The r4 artifacts above remain historical evidence bound to revision c3096e52bf1179b295840b2f5f24dd4708849499; they do not certify the current PR head. A fresh signed/reproducible candidate plus the remaining physical/VM checks tracked by #85 are still required before Windows release sign-off.