Identify and implement code reduction opportunities

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

Measured the tree with AST function clustering, dead-subject audit, jscpd 6/45 and six recon lanes: no decision-free reduction above ~25 lines remains. Top 5 opportunities (types.ts from OpenAPI, provisioner fold, legacy NodeLink wire, older-CP shims, legacy runtime) each need an ADR, a version floor or host verification; ranked in the report. No PR; no UI surface affected.