Top 5 Code Reduction Opportunities and 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 :)

Fifth reduction sweep: implemented the five largest measured folds (slot holder label single-homed in poolSlot, org_slug uses entity_shape.slug_taken, selftest checker shared, test scaffolding folded; −17 net lines, 13 files). Quick gate + changed-area tests + visual check green. PR #7600 queued to the merge lane. The thousands-of-lines levers (Windows/macOS support 22.5k, legacy CLI runtime 7.2k, agent-connectors 4k) are owner decisions, named in the report; live node-by-OS count unverified (bastion port-forward refused). Memory: used mem-32769; proposed 1 qa.