Reduce repository code by implementing top 5

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 :)

Re-measured the tree from six angles: the mechanical floor holds (86 removable Python lines, ~180 lines of scraps total) and the five massive cuts (MicroVM 28k, compliance 27k, Windows 12k, legacy runtime 11k, connectors+macOS 6k) are ADR-backed product retirements for the owner. Verified live via the console UI that the outcome-ledger backfill is done on dev but not yet shipped to main, so it stays. No PR. No UI surface affected. Memory: used mem-32769, mem-32704; proposed 1 recipe.