Identify and implement top 5 code reduction

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

Implemented the top 5 code reductions (net −315 lines, 128 files): api uuid/bool parse → entity_shape/jaah_env (90 sites); jaahd call sites → _sh/json_object/now_iso/parse_git_bool (fixes install vs check on/off mismatch); retired seal _legacy_wait + pre-SES deliver_email; 12 web list bodies → ListStates; web editor/confirm/search/debounce copies → shared hooks. Quick gate, web (12,170), jaahd and API (27,771) suites green; review lane pass; PR #7138 queued to the merge lane. Decided to settle on queued (the lane merges; Jaah Deploy watch left to the lane's re-dispatch). Rejected with reasons: identity contraction, NodeLink v1 wire, EmailMailbox, cloud-row fallbacks. Draft Task 10630 filed: 20 tools/tests suites no gate runs. Visual check done on 11 pages at 1280/448px, all good. Memory: used mem-27643, mem-27495; proposed 1 qa + 1 env.