Implement Five Repo 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 :)

Shipped the five largest ungated LOC cuts (one cron-minimum editor, one interstitial panel, one guarded file read + credential probe in jaahd, one wrapper strip for the shell guards, single-home stragglers): product −90 lines, tests +114. Honest finding: jscpd 0.22%, no massive ungated cut remains; the big ones (skynet aliases, _legacy_ columns, OpenAPI-generated web types) are gated and named as follow-ups. Blind review lane (security pass, code review fixes applied, verifier pass); ./dc check full green; visual check done on both cron editors and the three interstitials (desktop + 390px), all clean. PR #5446 merged into develop at d4810c952; Jaah Deploy succeeded. Deferred: the Settings › Organizations Access table clips its Remove action (task_create is refused to this persona). Memory: mem-15536, mem-16074, mem-16764, mem-10065 shaped the work; proposed mem-17120, mem-17121.