Why
The Navigation section describes a "Home" screen with category tile navigation that does not exist, which will cause any agent or contributor following the README to implement against a ghost architecture.
Current state
ui/tui/README.md lines 175–186 describe a Home screen with category preview tiles and Tab/Shift-Tab keybinds:
**Home** — category preview tiles
| Key | Action |
| ---------- | -------------------- |
| Tab | next tile |
| Shift-Tab | prev tile |
...
ui/tui/src/state/types.rs defines only two Screen variants:
pub(crate) enum Screen {
UnifiedList { ... },
Detail { ... },
}ui/tui/src/input.rs has no Tab binding and no home_keys function. The top-level view is UnifiedList, not a tile-based Home screen.
The Navigation section also labels the second level "Category" (lines 190–203) but the actual screen for that level is UnifiedList.
Ideal state
- The Navigation section describes
UnifiedList and Detail as the two screens — no "Home" or "Category" level that doesn't exist.
- Keybinds in the table match what is actually mapped in
input.rs — no Tab or Shift-Tab entries.
Starting points
ui/tui/README.md lines 173–217 — the Navigation section to rewriteui/tui/src/state/types.rs — authoritative Screen enumui/tui/src/input.rs — authoritative keybind mappings (unified_list_keys, list_keys)
QA plan
- Read the Navigation section of
ui/tui/README.md — expect two levels: UnifiedList and Detail, with no "Home" or "Category" heading.
- Search the README for
Tab and Shift-Tab in the Navigation section — expect zero matches.
- Cross-check each keybind listed against
input.rs — expect every row in the table to have a corresponding branch in unified_list_keys or list_keys.
Done when
The Navigation section of ui/tui/README.md describes only the screens and keybinds that actually exist in input.rs.
Why
The Navigation section describes a "Home" screen with category tile navigation that does not exist, which will cause any agent or contributor following the README to implement against a ghost architecture.
Current state
ui/tui/README.mdlines 175–186 describe a Home screen with category preview tiles andTab/Shift-Tabkeybinds:ui/tui/src/state/types.rsdefines only twoScreenvariants:ui/tui/src/input.rshas noTabbinding and nohome_keysfunction. The top-level view isUnifiedList, not a tile-based Home screen.The Navigation section also labels the second level "Category" (lines 190–203) but the actual screen for that level is
UnifiedList.Ideal state
UnifiedListandDetailas the two screens — no "Home" or "Category" level that doesn't exist.input.rs— noTaborShift-Tabentries.Starting points
ui/tui/README.mdlines 173–217 — the Navigation section to rewriteui/tui/src/state/types.rs— authoritativeScreenenumui/tui/src/input.rs— authoritative keybind mappings (unified_list_keys,list_keys)QA plan
ui/tui/README.md— expect two levels:UnifiedListandDetail, with no "Home" or "Category" heading.TabandShift-Tabin the Navigation section — expect zero matches.input.rs— expect every row in the table to have a corresponding branch inunified_list_keysorlist_keys.Done when
The Navigation section of
ui/tui/README.mddescribes only the screens and keybinds that actually exist ininput.rs.