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

Top 5 code-reduction folds shipped as PR #7579 (merged by the lane, f1994df): edit pages on useEditRecord, formatters single-homed, slot→console request once, guard scaffolding out of check_gh_pr_guard, jaahd runner/group folds. Net −62 source lines; quick gate + 2,500 changed-area tests green; blind code+security review clean; visual check done (playbook/template edit pages desktop+phone render unchanged). Honest finding: repo is at the mechanical floor (knip 0 dead files, vulture 0 dead defs); the massive levers (OpenAPI types.ts, mutation-score test pruning, Node/Host shell, legacy runtime, cloud token cache) each need a product decision and are listed in the report. Deploy for the merge was superseded by a later develop push and left alone per project directive. Memory: used none; proposed 1 qa + 1 recipe.