Profile visibility settings: design concepts

Follow-up to #57786. The behavior described there is working as designed, but the UI is confusing enough that several people have hit it. Filing the design follow-up. Looking for designer input. Not implementing yet. The problem <img width="1124" height="664" alt="Image" src=" /> Two independent visibility controls per field. Scope (lock icon) governs the address book, federation, and lookup server. Profile-page visibility (separate section) governs /u/<uid>. They sit far apart, use different vocabulary, and have different per-field defaults, so identical scope settings produce visibly inconsistent results. Goal: one control change should produce a predictable outcome. Underlying privacy model and per-field granularity stay. Concepts Five rough directions. Copy/icons illustrative; nothing final. A. Relabel and co-locate. Two controls stay, sit next to each other, clearer labels. <img width="1144" height="524&q…