Organize account controls into tabs

2026-07-25 01:15:15 -04:00
parent c286d1783d
commit 3c9f443499
3 changed files with 79 additions and 28 deletions
@@ -58,6 +58,13 @@ Use the spacing tokens for new components. Prefer `8px`, `12px`, and `20px` gaps
 - Account pages should read as an agent dossier: identity and access at the top,
  activity metrics beside it, archives in the primary column, and security
  controls in a narrower console column.
+- Dense account consoles use a tabbed control surface for profile, credentials,
+  linked identities, and account lifecycle actions. Only one panel is shown at
+  a time; validation failures reopen the panel containing the failed action.
+  Closely related mutually exclusive workflows, such as selecting a preset
+  portrait or uploading a custom portrait, use a compact secondary tab row.
+  Tabs retain native button semantics plus tablist, tab, and tabpanel roles,
+  textual selected state, keyboard focus, and pressed feedback.
 - Authentication pages use a split frame: contextual SHD network information on
  the left and the actionable secure-access console on the right.
 - OAuth providers appear as connection nodes with a recognizable provider color;