Settings page polish for org admins (seen

Seen on prod as a TimeSaver Org Admin while photographing Settings for the docs (Task 6654). Fix each: 1. Infrastructure > Range starts shows a monospace line "block 10 · stride 1 · window 1000 · tier-2 pool 20800–32767 (edit in the knobs above)", but an org admin can't edit the knobs above (they say "Set by an operator"). Drop the "edit in the knobs above" hint for non-operators and write the line in plain words instead of internal terms like "tier-2 pool". 2. Infrastructure > Ports shows "Stride 1 ports". Use the singular for 1 ("1 port"). 3. NodeVault, not set up yet, shows only a lone **Set up** button. Add one line saying what NodeVault does and link its docs page, like other empty states. 4. **Discard** and **Save** sit at the top of every category, even ones with nothing the viewer can edit (Tasks, Runners, Accounts for an org admin). Hide them when the category has no editable row, or show them only while there are unsaved changes. Out of scope: changing which settings an org admin may edit; operator-only views. Done means: each item above shows the fix on the live stack as an Org Admin (screenshot per item); `./dc check full` green.

All 4 Settings fixes for Org Admins merged in PR #5600. Range starts line in plain words with no edit hint; "1 port"; a NodeVault intro line with a docs link; Save/Discard only where editable or unsaved. Full gate green; visual check done on the live stack. Follow-ups filed as draft #6680. Deploy run was replaced by a newer push.