plans: status bar, round 3 -- detached survives, the drawer derives the keymap, decisions split from questions

Author: gluck

plans/status-bar-and-modes.md

@@ -64,25 +64,32 @@ reader notices on day one, so it is stated rather than discovered.
 
 ## 2. One owner for "what is open"
 
-**`keyMode` stays exactly as it is.** Keyboard behaviour and visible identity
-are different axes — `help`, `status` and `queue` share `modePanel` while being
-three different things on screen — and merging them buys nothing for input mode
-or multiplexing.
+Keyboard behaviour and visible identity are **different axes** — `help`,
+`status` and `queue` share `modePanel` while being three different things on
+screen — so they keep two types. But they are not independent: **the drawer
+identity is the source, and `keyMode` is derived from it.**
 
-What changes is smaller: **the drawer is the single owner of presentation**, and
-one table keyed by drawer id gives its glyph and name.
+```go
+func (d drawerID) keys() keyMode   // command → modeJump, search → modeSearch, panels → modePanel
+```
+
+That is the whole change, and it is what makes "one owner" true rather than
+aspirational: today `mode()` derives a `keyMode` from `inSearch`/`inJump` while
+the drawer tracks the same fact separately, so for one frame they can disagree.
+Opening a drawer becomes the only transition, the boxes keep their buffers, and
+nothing else reads those booleans.
+
+One table keyed by drawer id gives the glyph and the name.
 
 | drawer | mode glyph | name | selection glyph |
 |---|---|---|---|
 | queue | `𝄚` | queue | `♭` |
-| notifications | `𝄞` | notifications | `𝄞` *(see open questions)* |
+| notifications | `𝄞` | notifications | `𝄞` |
 | command | `∴` | command | — |
 | search | `∴` | search *(see open questions)* | — |
+| *(reserved)* | | input | |
 | help / status / message | `?` `!` — | help / status | — |
 
-`inSearch`/`inJump` stop being consulted by anything but the box that owns them;
-the bar and the keymap ask the drawer. Reserved for input mode: one more row.
-
 ## 3. `turnState`: symbol, name, colour
 
 ```go
@@ -98,10 +105,16 @@ func (s turnState) style() term.Style       // hup gray, error red, rest default
 | done | `✓` | `done ✓` | turn complete, no hup |
 | hup | `!` | `hup !` (gray) | user hangup |
 | error | `✗` | `error ✗` (red) | hup due to error |
-| idle | `𝄐` | `idle 𝄐` | **the catch-all** |
+| detached | `⠸` | `detached ⠸` | this CLI left; the turn continues |
+| idle | `𝄐` | `idle 𝄐` | **the catch-all**: none of the above |
+
+**`detached` keeps its meaning and loses its animation.** The first draft of
+this plan deleted it — a spinner that never turns again, since nothing repaints
+after a detach. But the animation was the defect, not the fact: "I left and the
+turn is still running" is precisely when the follow hint applies, and `idle` is
+defined as the catch-all for conditions *not otherwise known*. A static glyph
+keeps the truth and drops the lie.
 
-**`disconnected ⠸` is deleted** — a spinner that never turns again, since
-nothing repaints after a detach. It folds into `idle`, the declared catch-all.
 **Hup is a state, not an error**: the spec says so, and it is why hup is gray.
 
 ## 4. Notifications: a sink, a drawer, and nothing clever
@@ -151,27 +164,38 @@ everything else, and it inherits cost and the cache buckets from §1.
 
 Each step ships alone; none changes what the pager can do.
 
-1. **`turnState`** (§3) — smallest, and `statusView` needs it. Deletes
-   `disconnected`.
-2. **`statusView` + goldens** (§1) — the bar renders from a value.
-3. **The drawer table** (§2) — glyphs and names in one place; the bar stops
-   re-deriving what is open.
+1. **`turnState`** (§3) — smallest, and `statusView` needs it.
+2. **The drawer table** (§2) — glyphs, names, and `keys()`. It comes BEFORE the
+   value that consumes it: `statusView` takes a `drawerID` and renders its
+   glyph, so building the value first would mean re-deriving identity inside it,
+   which is the exact defect §2 exists to remove.
+3. **`statusView` + goldens** (§1) — the bar renders from a value.
 4. **`cmdkit.AndMore(n, hint)`** — one spelling of "… 749 more" for the drawer,
    `form show` and the `ls` family, which have three today.
 5. **notifications** (§4) — the only new surface.
 6. **`^V`** (§5) — last: the only binding change.
 
-## Open questions
+## Decided for you — each reversible with one line
 
-1. **Does the aria id move off the rule into the status row?** Every worked
+1. **The aria id moves off the rule and into the status row.** Every worked
    example shows a bare rule and `✓ · 123abc · test`; one sketch line says the
-   rule right-justifies the id. The examples are taken as authoritative here.
-2. **`∴` for both command and search?** One glyph for two modes works if the
-   name disambiguates — but the sketch labels the SEARCH row "command", so
-   either it is a typo or search has no identity of its own.
-3. **`𝄞` is asked to be both the notifications glyph and its selection cue.**
-   Two jobs, one symbol, on one screen. Which one gives way?
-4. **How does help "always work" when `?` is text?** Inside the command and
-   search boxes `?` is a printable character, so the requirement cannot mean
-   that key everywhere. Proposed: `:help` in the box, the hint row in every
-   mode, `?` everywhere else.
+   rule right-justifies the id. The examples win. Say the word and it flips
+   back.
+2. **`𝄞` is both the notifications glyph and its selection cue.** The spec asks
+   for a treble clef in both places and nothing says they must differ; an
+   aesthetic objection is not an ambiguity.
+3. **`cost` and the clock leave the bar** (§1), to the `!` panel.
+
+## Genuinely open
+
+1. **`∴` for both command and search?** The sketch gives search the `∴` glyph
+   and then labels its status row "command". Either a typo, or search has no
+   identity of its own and borrows command's.
+2. **How does help "always work" when `?` is text?** In the command and search
+   boxes `?` is a printable character, so the requirement cannot mean that key
+   everywhere — and `:help` cannot be the universal answer either, since `:` is
+   literal inside the SEARCH box (special-casing it would make that character
+   unsearchable). Proposed: **Esc-then-`?`** is the universal gesture, spelled
+   out in each box's hint row — which therefore must not be gated on verbose —
+   with `:help` kept as the command box's shortcut. This is a keyboard decision
+   and yours to make.