docs: the folding channel header in its e2e, and three comments brought up to date

The e2e asserted the channel chrome never moves; it folds once now. The ui catalog lists scrollFold and progressiveRows, Tabs names the per-tab memory its callers use, and the welcome note says a removed language orphans its stored copies too.
2026-10-02 23:42:32 +02:00
parent 608fde2d55
commit dfd43ae89c
4 changed files with 22 additions and 14 deletions
@@ -9,7 +9,8 @@ import CountBadge from "./CountBadge";
 // Below it a side rail leaves a phone too little width for the content beside it (measured at 390 px:
 // the rail clipped its own labels and Settings → Account pushed its buttons over their text), so there
 // it is a horizontal row that scrolls. Callers persist the active tab with lib/storage's
-// useAccountPersistedState (account-scoped), so a reload keeps the user where they were.
+// useTabPersistedState (per browser tab, E31 S4b): a reload keeps the user where they were, and a
+// fresh tab opens on the first sub-tab rather than wherever the last visit ended.
 //
 // An ARIA tab list (E28 review F3), not a row of toggle buttons: `tablist` / `tab` / `aria-selected`,
 // ONE Tab stop (the selected tab; roving tabindex), the arrows move and select (either axis, since the