Top 5 Code Reduction Opportunities Implementation

Identify top 5 opportunities to massively reduce the amount of code (lines of code) in any part of the repo: - Similar functionality that can be unified and reused - Code that has been valuable but no more - A front end component or a group of them duplicate another component/page functionality. Use the most modern and nice looking - etc. Now implement them :)

Mechanical ceiling re-measured from six angles: no production fold left; the five massive levers (Windows ~15k, MicroVM ~19k, macOS ~8k, legacy CLI runtime ~10k, compliance ~35k) are ADR-backed product decisions, tabulated in the report, not taken unattended. Shipped the safe reductions (−620 lines: suite-default folds in WorktreePool/NodeDetailPage/alert_relay tests, 16 test headers to the 12-line cap, AST-verified). Quick gate pass; review lane PASS, its findings fixed. PR #7625 queued to the merge lane (lane merges and deploys after this settle). No UI surface affected. Deferred: outcome-ledger backfill deletion once completed in every env (cp_psql refused). Memory: used mem-32769, mem-32704; proposed none (refused locator_only).