docs(framing): bottom-panel revision 7 --- per-kind mode line, geometry identity, and three half-fixes

Answers review of revision 6. Still framing only; no implementation.
Three of the five are corrections to rules 6 introduced.

**R-c's "the last row is inert" WAS WRONG.** The TUI precedent I cited
is per KIND, not per row: `inner_rows` guards `Down(Left)` (:3303),
`Drag(Left)` (:3331) and `Down(Right)` (:3348), and deliberately does
NOT guard `Up(Left)` (:3339) or the wheel (:3358/:3362). A blanket
inert rule breaks two things at once --- a wheel over the mode line
stops scrolling, and a gesture begun in content and released over the
mode line NEVER TERMINATES.

And a receiver-only rule cannot work at all here, because the producer
arms first: `PanelCell` spans the whole frame, so a mode-line `Down`
runs `set_panel_pointer_held(true)` locally
(`pmacs-gpu/src/main.rs:2878`) before the daemon sees anything.
Dragging into content then emits an orphan `Drag` the daemon cannot
tell from a real one. R-c now carries a per-kind producer/receiver
table, both crossings as witnesses --- mode-line->content must emit no
Drag, content->mode-line must terminate --- and rules the wheel
explicitly.

**R-d COVERED PANEL IDENTITY AND MISSED GEOMETRY IDENTITY.** The two
epochs move independently by design: `panel_epoch` is stable across
ordinary frames while `geometry_epoch` moves on any new declaration
"including a font or scale change that leaves `CellSize` identical"
(`pmacs-protocol/src/panel.rs:61`). `next_geometry_declaration`
(`pmacs-gpu/src/main.rs:6847`) advances it and clears neither pointer
field, so a held gesture resumes UNDER A NEW GRID carrying epochs that
are current and valid --- acceptance 49 rejects stale epochs and this
one is not stale.

R-d also constrained only one of the two latch fields. Clearing
`pointer_held` alone kills the orphan drag but leaves
`last_pointer_cell`, and `panel_motion_is_new` (`:7238`) then
suppresses the successor's first same-cell `Move` as a duplicate. Four
mutations now, D1-D4, including the NEGATIVE one: an ordinary
same-identity refresh must not cancel a live gesture, or D1/D2 are
satisfiable by resetting on every frame and selection stops working.

**R-a WITNESSED ONLY THE TERMINAL.** `dispatch_pointer`'s `Down` arm
reads `extending = mods.contains(SHIFT)` and either keeps the anchor or
collapses the selection (`src/editor.rs:3673`), so Shift-click in a
document or listview panel is selection extension. Threading modifiers
into `apply_terminal_gesture` alone would have passed the proposed row
while leaving document panels broken --- a witness certifying half a
fix. Two rows now, A1 terminal and A2 document, with separate
mutations: a single "drop mods at the boundary" bites both and proves
the boundary matters, not that each CONSUMER is wired.

**R-b'S ROWS WERE SATISFIABLE BY DOING NOTHING.** "Only A's panel
changes" passes for an implementation that drops the tail entirely. B1
now pins A's anchor at the Down cell's byte and A's cursor at the Drag
cell's byte; B2 proves `Up` collapses an empty click. B4 and B5 carry
Q#BP16's existing multi-click and Context statements, which replay is
where they first become executable. B6 is a listview visit sentinel:
the row is selected and `on_visit` does NOT run, so Q#BP-R1's ruling is
falsifiable rather than merely asserted.

Gates: all nine green under `env -u TMPDIR`, log 20260814T120856Z.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai

docs/active-work.md

@@ -281,9 +281,12 @@ from #171 and #215 — the correction the 1b lane missed, honoured here.
   **`githubsucks/panel-pointer-replay` is the authoritative tip** (the
   ref, not a SHA). Recover with
   `git fetch githubsucks && git checkout panel-pointer-replay`.
-- **No PR yet. Checkpoint: framing revision 6 (§5a) AWAITING APPROVAL;
+- **No PR yet. Checkpoint: framing revision 7 (§5a) AWAITING APPROVAL;
   NO IMPLEMENTATION WRITTEN.** Commit one was the ground-truth
-  re-measurement; **commit two answers review of it.**
+  re-measurement; 6 added the four replay edges; **7 answers review of
+  6** — R-c is per-KIND with a producer rule, R-d covers geometry
+  identity and both latch fields, R-a gains the document Shift
+  contrast, R-b's rows now pin results.
 - **Why this lane exists.** `PanelPointer` **replays nothing**:
   `dispatch_semantic_panel_pointer` (`src/editor.rs:2674`) validates,
   focuses, returns. A panel wheel is dead on both axes and so is every
@@ -339,17 +342,27 @@ from #171 and #215 — the correction the 1b lane missed, honoured here.
     is `rows − 1` (`src/editor.rs:2499`–`:2500`) but `panel_hit_test`
     reports across the whole frame (`pmacs-gpu/src/main.rs:7184`), so a
     `PanelPointer` can name the **mode-line row**. Terminal viewport is
-    `rows − 1`; document replay follows the TUI's *"Mode-line click:
-    reserved"* (`src/editor.rs:3304`–`:3306`). Rows must distinguish
-    content from chrome or an off-by-one passes.
+    `rows − 1`. **The document rule is PER KIND, not "the row is
+    inert"** — the TUI guards `Down(Left)`/`Drag(Left)`/`Down(Right)`
+    and deliberately not `Up(Left)` or the wheel, so a blanket rule
+    would stop mode-line scrolling and leave a content-started gesture
+    unterminated. **The producer must also not arm** on a mode-line
+    press (`pmacs-gpu/src/main.rs:2878`); a receiver-only rule cannot
+    stop the resulting orphan.
   - **R-d — replacement leaves the gesture latch armed.** `Absent`
     clears `pointer_held`/`last_pointer_cell`
     (`pmacs-gpu/src/main.rs:6909`) but **`Present`→`Present` does not**
     (`:6913`). A press on A then A→B emits a Drag/release for B with no
     B press, and **acceptance 49 cannot reject it** — the event carries
     B's *current* epochs. The **divider** drag latch already
-    epoch-scopes itself (`:7288`); the pointer latch never did. Reset
-    on presentation-identity change, mutation-checked.
+    epoch-scopes itself (`:7288`); the pointer latch never did. **Both
+    epochs**: a font/scale change advances `geometry_epoch` while
+    `panel_epoch` holds (`pmacs-protocol/src/panel.rs:61`) and clears
+    neither field, so a held gesture resumes under a new grid with
+    valid epochs. **Both fields**: clearing only `pointer_held` leaves
+    the successor's first same-cell `Move` suppressed as a duplicate
+    (`:7238`). Four mutations, including the negative one — an ordinary
+    same-identity refresh must NOT cancel a live gesture.
 - **RULED: Q#BP-R1** — a single click **SELECTS a listview row only**.
   RET/SPC remain activation (`listview.lua:610`); no click-to-visit and
   no double-click-to-visit. Keeps document navigation from becoming an

docs/bottom-panel-framing.md

@@ -7,7 +7,37 @@ protocol v20, 2026-07-24. Amended by the pre-implementation dependency
 verification in §0.6: the folding dependency is cleared, and one geometry
 caller-census error is corrected.**
 
-**Revision 6 — 2026-08-14, AWAITING APPROVAL.** Answers review of 5.
+**Revision 7 — 2026-08-14, AWAITING APPROVAL.** Answers review of 6.
+Five contract gaps, three of them corrections to 6's own rules:
+
+- **R-c's "the last row is inert" was wrong.** The TUI's rule is **per
+  KIND**: `inner_rows` guards `Down(Left)`/`Drag(Left)`/`Down(Right)`
+  and deliberately does not guard `Up(Left)` or the wheel. A blanket
+  rule would stop mode-line scrolling and leave a content-started
+  gesture unterminated. **And the producer arms before the receiver can
+  refuse** — a mode-line `Down` sets `pointer_held` locally
+  (`pmacs-gpu/src/main.rs:2878`), so a receiver-only rule cannot
+  prevent the orphan. R-c now carries a per-kind producer/receiver
+  table, both crossings, and an explicit wheel ruling.
+- **R-d covered panel identity but not GEOMETRY identity.** A font or
+  scale change advances `geometry_epoch` while `panel_epoch` holds, and
+  the transition clears neither pointer field, so a held gesture
+  resumes under a new grid with *current, valid* epochs. Four
+  mutations now, including the **negative** one: an ordinary
+  same-identity refresh must not cancel a live gesture.
+- **R-d also needed `last_pointer_cell` constrained separately** —
+  clearing only `pointer_held` leaves the successor's first same-cell
+  `Move` suppressed as a duplicate.
+- **R-a witnessed only the terminal.** The document path consumes Shift
+  too, for the selection anchor, so threading modifiers into
+  `apply_terminal_gesture` alone would pass the proposed row while
+  breaking Shift-click in document and listview panels.
+- **R-b's rows were satisfiable by doing nothing.** They now pin A's
+  anchor and cursor after the Drag, prove `Up` collapses an empty
+  click, and carry Q#BP16's multi-click and Context semantics plus a
+  listview visit sentinel for Q#BP-R1.
+
+**Previously, revision 6 — SUPERSEDED.** Answered review of 5.
 **Q#BP-R1 is RULED: a single click SELECTS a listview row only**;
 RET/SPC remain activation, and this lane adds no click-to-visit.
 Revision 5 concluded that the activation ordering made replay safe;
@@ -1896,11 +1926,27 @@ is the user's override for "select locally instead of talking to the
 child."** Arriving with modifiers zeroed, a Shift-drag over a
 reporting terminal panel sends SGR to the child instead of selecting.
 
-**Thread `mods` through** the destructure, the dispatcher signature and
-into `apply_terminal_gesture`. **Row:** with mouse reporting enabled,
-a Shift-drag selects locally and the child receives **no bytes**.
-*Mutation: drop `mods` at the daemon boundary — the child receives
-bytes and the row fails.*
+**And the terminal is not the only consumer.** The ordinary document
+path reads Shift too: `dispatch_pointer`'s `Down` arm computes
+`extending = mods.contains(SHIFT)` and `keep_anchor`, then either
+**extends from the previous cursor** or collapses the selection to the
+clicked byte (`src/editor.rs:3673`–`:3687`). So Shift-click in a
+**document or listview panel** is selection extension, and threading
+modifiers *only* into `apply_terminal_gesture` would **pass the
+terminal row while leaving document panels broken** — the exact shape
+of a witness that certifies half a fix.
+
+**Thread `mods` through** the destructure, the dispatcher signature,
+and into **both** consumers. Two rows, and both mutations:
+
+| # | row | mutation |
+|---|---|---|
+| A1 | terminal panel, reporting enabled: **Shift**-drag selects locally, child receives **no bytes** | drop `mods` before `apply_terminal_gesture` → the child receives bytes |
+| A2 | document/listview panel: **Shift**-click **extends** the selection from the prior cursor; unmodified click collapses it | drop `mods` before the document path → Shift-click collapses, A2 fails while A1 still passes |
+
+A2's mutation is deliberately separate from A1's: a single "drop
+`mods`" at the boundary bites both, which proves the boundary matters
+but not that **each consumer** is wired.
 
 #### R-b. Activation does not make the document path target-safe
 
@@ -1922,13 +1968,28 @@ the round-3 F1 correction) **but it also calls
 (`set_cursor_byte`, `begin_selection`) write `active_window_mut()`.
 Panel replay needs the conversion **without** the ambient write.
 
-Two rows, both of which a naive implementation fails:
+**The witnesses must pin the RESULT, not just the absence of collateral
+damage.** "Only A's panel changes" is satisfied by an implementation
+that drops the tail entirely and changes nothing anywhere.
 
-- **Interleaved frontend:** panel A `Down` → **frontend B input** →
-  panel A `Drag`/`Up`. **Only A's panel changes.**
-- **Orphan gesture:** a `Drag`/`Up` against a **passive** panel with no
-  preceding `Down`. **The document mirror is byte-identical
-  afterwards** — cursor, selection and `view_top`.
+| # | row | what it pins |
+|---|---|---|
+| B1 | panel A `Down` → **frontend B input** → panel A `Drag` | A's **anchor is the Down cell's byte and A's cursor is the Drag cell's byte**, exactly; B's window and the document mirror are unchanged |
+| B2 | panel A `Down` → `Up` at the **same** cell | the empty selection **collapses** — an Up that does nothing leaves a stale one-byte region |
+| B3 | orphan `Drag`/`Up` on a **passive** panel, no preceding `Down` | the document mirror is **byte-identical**: cursor, selection, `view_top` |
+| B4 | **repeated left `Down`s** at one cell | the existing daemon click state reads a **multi-click**, per Q#BP16 — so replay must not swallow or coalesce them |
+| B5 | `Down(Right)` on a panel cell | the **context menu** opens, per Q#BP16 — a right press is not a selection gesture |
+| B6 | click a **listview** row | the row is **selected** and `on_visit` **does not run** — a sentinel proving Q#BP-R1's ruling holds through replay |
+
+B4 and B5 are not new contracts: Q#BP16 already states that repeated
+left `Down`s are what the click state reads as a multi-click and that
+`Down(Right)` is the context gesture, *"so neither may collapse"*
+(§3, Q#BP16). They are in this matrix because **replay is where those
+statements first become executable** — until now nothing replayed, so
+nothing could contradict them.
+
+B6 is the sentinel for the ruling above: selection without activation
+is only meaningful if something fails when a click visits.
 
 #### R-c. `panel_grid_size` is the FRAME, not the terminal viewport
 
@@ -1945,16 +2006,49 @@ child is told about a row it does not own, and every coordinate below
 it is off by the same row when the size is used for clamping.
 
 - **Terminal panels:** the viewport is **`rows − 1`**.
-- **Document panels:** the mode line needs an **explicit rule**, and
-  the TUI already has one — `dispatch_mouse` returns early on
-  `local_row >= inner_rows` with the comment *"Mode-line click:
-  reserved."* (`src/editor.rs:3304`–`:3306`). **Panel replay follows it**: a
-  mode-line gesture is reserved, not a click at the nearest content
-  cell.
+- **Document panels:** the mode line needs an explicit rule.
 
-**Rows must distinguish content from chrome**: a gesture on the last
-row is inert (and reaches no child), while the same gesture one row up
-replays normally. Without that pair, an off-by-one passes.
+**"The last row is inert" is WRONG, and revision 6 said it.** The TUI's
+rule — which is the precedent — is **per kind**, not per row.
+`inner_rows` guards `Down(Left)` (`src/editor.rs:3303`), `Drag(Left)`
+(`:3331`) and `Down(Right)` (`:3348`), and **`Up(Left)` (`:3339`),
+`ScrollUp` (`:3358`) and `ScrollDown` (`:3362`) are deliberately NOT
+guarded.** A blanket
+"inert" rule would break two things at once: a wheel over the mode line
+would stop scrolling, and a gesture that begins in content and releases
+over the mode line would **never terminate**.
+
+**And the producer arms before the receiver can refuse.** `PanelCell`
+comes from `panel_hit_test`, which spans the whole frame, so a
+mode-line `Down` runs `set_panel_pointer_held(true)` **locally**
+(`pmacs-gpu/src/main.rs:2878`–`:2880`) before any daemon decision.
+Dragging from there into content then emits a `Drag` with no accepted
+`Down` — an orphan the daemon cannot distinguish from a real one. **A
+receiver-only rule cannot fix this**; the producer must not arm on a
+mode-line press.
+
+| kind on the mode-line row | producer | receiver |
+|---|---|---|
+| `Down(Left)`, `Down(Right)` | **do not arm, do not send** | reserved — drop |
+| `Drag(Left)` | not sent (never armed) | reserved — drop |
+| `Up(Left)` | **send** — it terminates a gesture begun in content | **process**, terminating the gesture |
+| wheel | **send** | **process** — scrolls the panel, per the TUI |
+
+**Both crossings need witnesses, and they fail in opposite
+directions:**
+
+- **Mode line → content:** press on the mode line, drag into content.
+  **No `Drag` reaches the daemon**, because nothing armed. *Mutation:
+  arm on a mode-line press — the orphan appears.*
+- **Content → mode line:** press in content, release over the mode
+  line. **The gesture terminates** — the selection is committed, the
+  latch clears. *Mutation: reserve `Up` as well — the gesture hangs,
+  latched, and the next unrelated motion continues a selection the user
+  ended.*
+
+**The wheel is ruled explicitly**: a wheel over the mode line scrolls
+the panel exactly as one over content does. It is not a click, it
+carries no position semantics, and the TUI does not guard it.
 
 #### R-d. Panel replacement leaves the frontend's gesture latch armed
 
@@ -1970,15 +2064,48 @@ not stale by any test 49 applies. 49 is a staleness gate, and this is
 not a stale event; it is a **well-formed event from a gesture that
 belongs to a presentation that no longer exists.**
 
-**Reset the gesture latch on presentation-identity change.** The
-precedent is in the same file: the **divider** drag latch already
-carries `panel_epoch`/`geometry_epoch` and self-invalidates when the
-presented frame's epochs differ (`:7288`). The pointer latch simply
-never got the same treatment.
+**And panel identity is only half of it.** The two epochs move
+independently, by design (`pmacs-protocol/src/panel.rs:61` onward):
+`panel_epoch` is *"stable across ordinary frames of one continuously
+present window/buffer"*, while `geometry_epoch` *"moves whenever the
+frontend declares new effective cell geometry — including a font or
+scale change that leaves `CellSize` identical"*. A font or scale change
+therefore advances `geometry_epoch` with `panel_epoch` untouched, and
+`next_geometry_declaration` (`pmacs-gpu/src/main.rs:6847`) advances it
+**without clearing either pointer field**.
 
-*Mutation: omit the reset on `Present`→`Present` — the orphan-drag row
-fails.* Distinct from R-b's orphan row: that one arrives from a
-**passive** panel, this one from a **replaced** one, and an
+So a held gesture **resumes under a new grid** — new cell advance, new
+row heights, the same cells meaning different text — carrying epochs
+that are *current and valid*. Acceptance 49's geometry-race check
+cannot help: it rejects events bearing a **stale** `geometry_epoch`,
+and this one bears the new one.
+
+**Reset the gesture latch on a change of EITHER identity.** The
+precedent is in the same file: the **divider** drag latch already
+carries both epochs and self-invalidates when the presented frame
+differs in either (`:7288`). The pointer latch never got it.
+
+**Both fields, and both must be constrained separately.** Clearing only
+`pointer_held` kills the orphan drag but leaves `last_pointer_cell`
+set, and `panel_motion_is_new` (`:7238`–`:7242`) then **suppresses B's
+first same-cell `Move` as a duplicate** — the successor's opening
+motion silently vanishes. The fields fail differently and need
+independently discriminating legs.
+
+| # | mutation | must bite |
+|---|---|---|
+| D1 | no reset on `Present`→`Present` (panel identity) | the replaced-panel orphan-drag row |
+| D2 | no reset on `geometry_epoch` change | the font/scale held-gesture row |
+| D3 | reset clears `pointer_held` only | the successor's first same-cell `Move` row |
+| D4 | reset on **every** frame | the negative row below |
+
+**The negative leg is required**, or D1/D2 are satisfiable by resetting
+unconditionally: an **ordinary same-identity frame refresh must NOT
+cancel a live gesture**. A panel repaints constantly during a drag;
+resetting on each frame would make selection impossible.
+
+R-d's orphan is distinct from R-b's: **R-b's arrives from a passive
+panel, R-d's from a replaced or re-declared one**, and an
 implementation can fix either alone.
 
 ## 6. Deferred (named)