fix: stabilize v1.8.3 ports and desktop cleanup

[weidonglang]

Scope

Tracks #134.

This Draft PR contains the isolated v1.8.3 hotfix implementation only. It does not merge, tag, publish, bump the application version, or modify v1.8.2 release assets.

Ports and dashboard

• Replace the blocking one-shot port scan with a bounded quick snapshot plus asynchronous PID/process/service enrichment.
• Add recommended/full scopes, single-flight execution, a 20-second cache, last-success fallback, force refresh, cancellation, and redacted diagnostics.
• Fall back from timed-out netstat to filtered PowerShell JSON without treating TIME_WAIT/PID 0 as actionable records.
• Precisely deduplicate endpoint records and group equivalent IPv4/IPv6 bindings into one stable groupId row without losing binding details.
• Preserve structured scan-source evidence, fallback markers, timestamps, counts, and source conflicts.
• Keep Dashboard startup scanning background-only and isolate port failures to the port card.
• Bind plans to group/scan/process fingerprints and force a fresh owner/risk/binding check before execution.
• Verify target and related-port release after execution; another PID reoccupying the port is not reported as success.

Process identity

• Add the versioned process-identities.v1.json catalog with 39 identity families and 238 aliases.
• Use executable, service, path, command line, parent, file metadata, publisher, and port hints as independent evidence.
• Keep software confidence separate from operation risk; a filename or port alone cannot lower risk or authorize termination.
• Show friendly identity, confidence, evidence/conflicts, file metadata, services, bindings, and source evidence in the Ports details UI.
• Keep service-owned and protected Windows processes outside ordinary force-kill actions.

Cleanup and desktop workflow

• Restore readable disk-overview cards in dark and high-contrast themes, add explicit risk labels, and make the layout responsive.
• Add structured Desktop analysis with selectable eligible files, protected reasons, plan preview, copy/hash verification, receipts, rollback, and automatic restoration on partial failures.
• Keep Recycle Bin cleanup as a separate token-gated action that uses the Windows Recycle Bin instead of permanent deletion.

Acceptance and CI

• Extend the feature manifest, mock fixtures, stable selectors, data/action contracts, and frontend acceptance for grouped ports.
• Add catalog schema/duplicate/alias/policy checks.
• Run static, safe, frontend, and report acceptance modes in Windows CI and upload the generated reports/evidence as an artifact.

Automated verification for eb019a8

• Rust tests: 190 passed, 0 failed.
• Clippy: cargo clippy --all-targets -- -D warnings passed.
• Frontend: npm run build passed (110 modules).
• Frontend acceptance: 212 stable data-testid selectors found.
• Feature acceptance: 296 total, 252 passed, 0 failed, 37 safe-skipped, 7 manual.
• Isolated capability fixtures: 14/14 passed, including the temporary listener sandbox.
• Backend/UI drift, frontend data/action/quality/i18n, toast-only, Tauri command, repo hygiene, safety wording, and process catalog checks passed.

The 37 skipped and 7 manual cases are explicitly bounded to real Tauri state, privileged/dangerous mutations, installed-app validation, or v1.9.0 deferred scope; none is silently counted as passed.

Remaining release gates

• Latest GitHub CI for eb019a8 is green.
• Real high-connection Windows port scan completes without the previous timeout failure.
• Equivalent IPv4/IPv6 rows are grouped and PostgreSQL/Node/Java identities and confidence are reasonable.
• Dashboard background port scan does not block first render or unrelated cards.
• Disk overview is readable and not clipped in Dark and High Contrast themes.
• A disposable Desktop file completes analyze -> select -> plan -> execute -> restore.

This PR remains Draft until CI and the six focused real-machine checks are green. No RC or release action is included yet.