docs: archive Phase L L5 to COMPLETED; reconcile CLAUDE.md + CONTEXT.md + PLAN.md

CONTEXT.md

@@ -1583,12 +1583,12 @@ adds a **hover tooltip showing the FULL action name with the `ReaSampler:` displ
 stripped.** Note the prefix (`actionDisplayPrefix()`) is baked into the *registered gaccel
 action name*, not the button face — so the tooltip derives the full name and strips the prefix
 for display; the button face never carried the prefix. The keybinding stays on the existing
-`micro` sub-row. **Tooltip mechanism is a build-time choice (staff-engineer):** SWELL's tooltip
-control vs. a custom hover-delay kit tooltip. **Recommended: a custom hover-delay kit tooltip** —
-it owns its own hover timer + LICE overlay draw, stays inside the L1 kit (DS-1 "keep drawing in
-the kit"), and avoids attaching a SWELL tooltip control to non-child LICE rects (awkward for
-dynamically-tiled buttons). The hover-timer threshold + overlay draw are the only DAW-bound
-pieces; the "which button, what text" decision stays pure.
+`micro` sub-row. **Tooltip mechanism: custom LICE-kit hover-delay tooltip** (`tooltip` pure
+module) — owns its own hover timer + LICE overlay draw, stays inside the L1 kit (DS-1 "keep
+drawing in the kit"). Sourced from the registered action phrase (not `kbd_getTextFromCmd`);
+`ReaSampler:` prefix stripped at draw time; tooltip box width clamped to the client so it never
+overhangs a narrow dock. The hover-timer threshold + overlay draw are the only DAW-bound pieces;
+the "which button, what text" decision stays pure.
 
 **3. Bottom-toolbar Item/Track × Arrange/Design tag buttons, opposite-mode-only.** The current
 `Tag Design` / `Untag` pair is replaced by **four buttons — "Item: Arrange", "Item: Design",
@@ -1618,21 +1618,15 @@ bodies exactly (no selection semantics change).
 `[Arrange|Design]` toggle (L4) already covers mode switching. **The action stays registered**
 (keybinding-bound, FOREVER-STABLE id unchanged); only its *button home* is removed.
 
-**Fate of Activate-Arrange / Activate-Design / Show-Both (FORK — Daniel's call).** These three
-`Switching`-cluster buttons overlap the footer toggle to varying degrees:
-- `VIEW_ACTIVATE_ARRANGE` / `VIEW_ACTIVATE_DESIGN` — **direct** mode jumps. With the footer
-  toggle present, they are largely redundant on the bar (the toggle *is* an Arrange/Design
-  switch). **Recommendation: DROP both from the bottom toolbar** (actions stay registered), so
-  the footer toggle is the single mode-switch affordance and the bottom bar is tagging-only.
-- `VIEW_SHOW_BOTH` — the cross-mode "pin visible in every mode" escape hatch. It is **not**
-  covered by the footer toggle (it is a per-track pin, not a mode switch). **Recommendation:
-  KEEP it** — as a lone button, or folded into a small `⋯` bottom-bar menu alongside any other
-  rare view verbs.
-- **Recommended final bottom-toolbar inventory:** `[ Item: Arrange | Item: Design ] · [ Track:
-  Arrange | Track: Design ]  ⟩⟩  [ Show Both ]` — Tagging cluster (four opposite-mode buttons)
-  set apart from a lone `Show Both`. No Toggle, no Activate-Arrange/Design (footer toggle owns
-  switching). **Daniel decides whether to keep Activate-Arrange/Design as bar buttons and
-  whether Show-Both stays a button or moves to a menu.**
+**Fate of Activate-Arrange / Activate-Design / Show-Both (FORK — RESOLVED, Daniel's call).**
+- `VIEW_ACTIVATE_ARRANGE` / `VIEW_ACTIVATE_DESIGN` — **dropped from the bottom toolbar** (actions
+  stay registered, FOREVER-STABLE ids unchanged). The footer `[Arrange|Design]` toggle is the
+  single mode-switch affordance; the bottom bar is tagging + Show Both only.
+- `VIEW_SHOW_BOTH` — **kept** as a set-apart button on the bottom toolbar. It is the cross-mode
+  "pin visible in every mode" escape hatch and is not covered by the footer toggle.
+- **Landed bottom-toolbar inventory:** `[ Item: Arrange | Item: Design ] · [ Track: Arrange |
+  Track: Design ]  ⟩⟩  [ Show Both ]` — Tagging cluster (four opposite-mode buttons) set apart
+  from a lone `Show Both`. No Toggle, no Activate-Arrange/Design (footer toggle owns switching).
 
 **5. Semantic-grouping spacing.** L4's `kBarSpec` is `buttonGap=4` / `clusterGap=16` (4:1). With
 the bottom bar's cluster boundary now more meaningful (four tag buttons vs. the `Show Both`
@@ -1654,10 +1648,8 @@ editor (`IPlugView` LICE surface), the S6 embed strip, and the keyboard strip li
 Phase S, which is **not on dev yet** (it exists on the phase-s worktree). L3 cannot be
 built on dev until Phase S's editor/embed surfaces (≈ S1 / S6 / S10) merge to dev — **the
 Phase L team must not chase these files on dev; they are not there.** Until then L3 is a
-planned, blocked point; L1, L2, and **L4 (dock-panel button layout enhancement) have all
-landed**. L4 is independent of the L3 gate. **L5 (dock-panel button refinements — §L5 above)
-is the live forward Phase L point**: ungated by Phase S, sequences after L4, also independent
-of the L3 gate.
+planned, blocked point; L1, L2, L4, and **L5 have all landed** — see `COMPLETED.md`. L4 and L5
+are independent of the L3 gate.
 
 **Coordination contract (load-bearing):** Phase S's S10–S13 build their interaction UX with
 the **current** drawing and **adopt the L1 kit when it is available — they are NOT gated on