docs(framing): mark bottom-panel revision 12 approved

SS5a is the acceptance-48 ground truth and its rulings are settled:
Q#BP-R1 (a single click selects a listview row only), Q#BP-R2 (a
terminal-chrome wheel is consumed daemon-side, before activation), the
R-a..R-d replay edges, and the witness matrices A1-A5, B1-B6, D1-D4.

Also records what the eight rounds cost, because the pattern repeated:
every round found a witness or a rule that would have PASSED against a
broken implementation. A `#[cfg(test)]` fixture cited as a production
handler. Activation ordering mistaken for a safety proof. A mode-line
rule that was per-row when the tree's is per-kind, and document-only at
that. A producer rule the frontend had no information to obey. A
consume check that would have left focus stolen. And twice, an
assertion added without a state in which it could fail.

No round found a design disagreement. The rulings from 8 and 9 survived
intact; what changed each time was WHERE a rule lived or WHAT A WITNESS
COULD SEE.

Implementation begins.

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

docs/active-work.md

@@ -281,8 +281,8 @@ 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 12 (§5a) AWAITING APPROVAL;
+- **No PR yet. Checkpoint: framing revision 12 (§5a) APPROVED
-  NO IMPLEMENTATION WRITTEN.** Commit one was the ground-truth
+  2026-08-14; IMPLEMENTATION BEGINS.** Nothing gates this lane now. Commit one was the ground-truth
   re-measurement; 6 added the four replay edges; **7 answers review of
   6; **8 answers review of 7** — R-c is target × gesture-ORIGIN
   (terminals reject all chrome kinds and raw chrome coords fail the

docs/bottom-panel-framing.md

@@ -7,8 +7,26 @@ 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 12 — 2026-08-14, AWAITING APPROVAL.** Answers review of 11,
+**Revision 12 — 2026-08-14, APPROVED.** §5a is the acceptance-48
-whose witness had a **vacuous precondition**.
+ground truth and its rulings are settled: **Q#BP-R1** (a single click
+selects a listview row only), **Q#BP-R2** (a terminal-chrome wheel is
+consumed, daemon-side, before activation), the **R-a…R-d** replay
+edges, and the witness matrices A1–A5, B1–B6, D1–D4.
+
+**§5a took eight review rounds (5–12), and the pattern is worth
+keeping: every round found a witness or a rule that would have passed
+against a broken implementation.** A test fixture cited as a production
+handler; activation ordering mistaken for a safety proof; a mode-line
+rule that was per-row when the tree's is per-kind, and document-only at
+that; a producer rule the frontend had no information to obey; a
+consume check that would have left focus stolen; and — twice — an
+assertion added without a state in which it could fail. **No round
+found a design disagreement.** The rulings from 8 and 9 survived
+intact, and what changed each time was *where* a rule lived or *what a
+witness could see*.
+
+Revision 12 answered review of 11, whose witness had a **vacuous
+precondition**.
 
 "Focus unchanged" proves nothing if the terminal panel is **already
 focused**: the below-activation mutation then calls `focus_window` on