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

Measured the tree first (jscpd 0.22% duplication over 1.2M lines, 0 dead modules; every "dead" export is an edition seam), then folded the five real clone groups: web pieces, API route helpers, jaahd slot parse, tools scaffolding, test bodies. Net −99 lines over 24 files, no behaviour change. Quick gate green; 544 web, 265 API, 133 jaahd tests pass; visual check done at 1280px and 448px (org-scope picker, activity timeline, NodeLink page clean). PR #7437 queued to the merge lane. Named deferred: test-suite value audit (tests are 52% of the repo) and OpenAPI-generated TS types need an ADR, not a runner. Memory: none applied.