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

PLAN.md

@@ -391,13 +391,14 @@ they merge (same gate posture as L3).
 > directions: `docs/product/visual-design-language.md`. When a point lands, doc-keeper
 > moves it to `COMPLETED.md`.
 >
-> **L1 (shared LICE drawing kit — the foundation) and L2 (dock-panel layout redesign)
-> have landed** — `theme`/palette module, `component_geometry` geometry/hit-test helpers,
-> `draw_kit` shell, GDI `DrawText` retirement in `bank_panel` (L1); `action_bar` pure
-> task-grouped layout module, full M11-aware button inventory placed by task cluster,
-> `bank_panel` redesigned through the L1 kit (L2). See `COMPLETED.md`. **L3 and L4 remain**
-> — L3 gated on Phase S landing on dev; L4 (dock-panel button layout enhancement) ungated and
-> extension-side, sequencing after the in-flight palette revision merges to dev.
+> **L1 (shared LICE drawing kit — the foundation), L2 (dock-panel layout redesign), and L4
+> (dock-panel button layout enhancement) have landed** — `theme`/palette module,
+> `component_geometry` geometry/hit-test helpers, `draw_kit` shell, GDI `DrawText` retirement
+> in `bank_panel` (L1); `action_bar` pure task-grouped layout module, full M11-aware button
+> inventory placed by task cluster, `bank_panel` redesigned through the L1 kit (L2); three-zone
+> layout (top capture/placement/maintenance toolbar, bottom Design-View toolbar, footer toggle +
+> Tail button + Prune), `footer_bar` pure module, `ActionCluster::Tagging`/`Switching` in
+> `action_bar` (L4). See `COMPLETED.md`. **L3 remains** — L3 gated on Phase S landing on dev.
 >
 > **This section is self-contained for a team without Phase S context.** Where a point
 > touches a Phase S surface (the VST editor, the embed strip, the keyboard strip), the
@@ -474,85 +475,15 @@ work.
   state — never a pulse, per the speed constraint) as the signature surface; VST3 class UID
   unchanged. (Gated.)
 
-## L4 — dock-panel button layout enhancement (ungated, extension-side)
-**Goal:** Re-home the `bank_panel`'s L2 button inventory around *frequency and intent*, so the
-two acts the tool exists for (capture, placement) sit at the **top** where the eye lands, the
-Design View organize/switch verbs get a real button home at the **bottom**, and the footer
-carries the small persistent controls (the Arrange|Design toggle, Tail, Prune) in a coherent
-left-to-right order. This is a **layout re-home of buttons that fire existing actions** — no new
-actions, no capture/placement behavior change, no touching the "capture ≠ placement" principle.
-It is independent of L3 (which stays gated on Phase S); L4 is **ungated, extension-side only**
-(the dock panel lives on dev). Product framing: `docs/product/visual-design-language.md` §L4
-(new) + CONTEXT.md §Phase L "L4 dock-panel button layout".
-
-The four layout moves (Daniel, 2026-07-26):
-1. **Capture + placement clusters move to a TOP toolbar.** The capture cluster (capture item,
-   capture track, batch items, batch razor, capture RT) and the placement cluster (insert,
-   insert-conform) leave the current bottom L2 action bar and become a **top** toolbar — the
-   first thing the eye meets, matching their frequency and the tool's purpose.
-2. **The bottom toolbar is repurposed for Design View tagging + switching.** In the space the
-   capture/placement buttons vacate, place the Design View action family as buttons: **tag /
-   untag selected tracks for a mode, activate Arrange, activate Design, toggle active mode,
-   show-both.** These are registered actions today (the Design View action family); L4 gives
-   them a button home in the bottom toolbar.
-3. **The Arrange|Design segmented toggle shrinks and moves to the footer.** The large top
-   `[ Arrange | Design ]` segmented control shrinks to **just wide enough for its text
-   comfortably** and moves into the **footer, to the LEFT of the Prune button** (see footer
-   order below). The per-mode membership count travels with it (as a compact adjacent label).
-4. **Tail becomes a real button.** The Tail footer affordance is a **click-zone** today
-   (clicking cycles the tail setting) — inconsistent with the other footer controls. Convert it
-   to a proper **button** drawn through the L1 kit like the others; click still cycles the tail
-   setting, but it now reads and behaves as a button (rest/hover/pressed states).
-
-**Footer affordance order (left → right):** `[Arrange|Design]` toggle · Tail button · … ·
-**Prune** (set apart at the right, `warn`). *Rationale:* the two view/session controls (mode
-toggle, tail) group at the left as the "how this panel/capture behaves" cluster; Prune stays
-isolated at the far right, visually separated and `warn`-colored, because it is the only
-byte-deleting affordance and must never sit adjacent to a benign toggle where a mis-click is
-cheap. Order reads left (benign, frequent) → right (destructive, rare).
-
-**Verify (in DAW):** the top toolbar fires every capture + placement action; the bottom toolbar
-tags/untags selected tracks and switches/toggles Arrange/Design/show-both; the footer shows a
-narrow `[Arrange|Design]` toggle at the left, a Tail button that cycles tail on click with
-button states, and the Prune button set apart at the right in `warn`; every surface draws
-through the L1 kit in the DS-2 grey+pastel palette; capture and placement still never
-auto-insert (the buttons only fire the existing, unchanged actions).
-
-**Depends on:** L1 (the kit) + L2 (the landed layout + `action_bar` module). **Ungated by Phase
-S** — extension-side (`bank_panel`) only. **Sequence AFTER the palette revision merges to dev**
-— the in-flight DS-2 grey+pastel palette branch also reworks `bank_panel` heavily; landing L4
-concurrently would collide the same file. L4 begins once the palette revision is on dev.
-**Pure/shell discipline (unchanged):** all new toolbar/footer layout math goes in pure
-CTest-covered geometry modules — extend/mirror `action_bar` (toolbar row layout) and
-`mode_switch` (the now-narrow footer toggle); `bank_grid`/`tab_strip` stay owners of their own
-surfaces' hit-testing. The kit draws; geometry stays pure.
-
-- [ ] Top toolbar: re-home the capture cluster (item / track / batch items / batch razor /
-  capture RT) + placement cluster (insert / insert-conform) from the bottom L2 bar to a top
-  toolbar (pure row layout in `action_bar`; kit draw). Buttons fire the existing actions
-  unchanged — no auto-insert.
-- [ ] Bottom toolbar: place the Design View action family as buttons (tag / untag selected for
-  mode, activate Arrange, activate Design, toggle active mode, show-both), firing the existing
-  registered Design View actions.
-- [ ] Footer: shrink the `[ Arrange | Design ]` segmented toggle to fit-its-text width and move
-  it to the footer left of Prune (narrow-segment geometry in `mode_switch`); carry the per-mode
-  count as a compact adjacent label.
-- [ ] Footer: convert the Tail click-zone into a proper kit button (rest/hover/pressed states;
-  click cycles the tail setting as today).
-- [ ] Footer order: `[Arrange|Design]` · Tail · … · Prune (`warn`, set apart at the right);
-  pure footer-strip layout covered by CTest.
-
 ## Phase L — sequencing
 ```
 L1 (shared kit) ──► L2 (dock-panel layout redesign) [LANDED]
         ├─────────► L3 (VST editor + embed-strip restyle; GATED on Phase S landing on dev)
-        └─────────► L4 (dock-panel button layout enhancement; ungated, extension-side;
-                        sequences AFTER the palette revision merges to dev)
+        └─────────► L4 (dock-panel button layout enhancement) [LANDED]
 
 Phase S (separate team, ungated): S-work builds with current drawing, adopts L1 when it lands.
 ```
-L1 and L2 have landed. L3 waits for Phase S to reach dev. L4 is ungated and extension-side but
-sequences after the in-flight palette-revision branch merges to dev (both rework `bank_panel`).
+L1, L2, and L4 have landed. L3 waits for Phase S to reach dev.
 Phase S feature work runs in parallel, ungated by Phase L.
 
 ## Phase L — must-verify-before-build
@@ -570,11 +501,9 @@ Phase S feature work runs in parallel, ungated by Phase L.
   useful; keep hit-test geometry pure regardless.
 - **M11 button inventory (L2)** — resolved at L2 build: inventory taken against dev after
   M11 merged; all buttons placed by task cluster in the landed `action_bar` module.
-- **L4 re-home surface (L4)** — resolved at L4 build against the **post-palette-revision**
-  `bank_panel`: confirm the landed `action_bar` row-layout module and the `mode_switch`
-  segmented-toggle geometry extend cleanly to a top toolbar + a narrow footer toggle, and that
-  the Design View action family's command ids are all live for the bottom-toolbar buttons.
-  **Do not build until the palette revision is on dev** (shared-file collision).
+- **L4 re-home surface (L4)** — resolved at L4 build: three-zone layout confirmed against the
+  post-palette-revision `bank_panel`; `action_bar` extended with `ActionCluster::Tagging` +
+  `Switching`; new pure `footer_bar` module covers footer layout/hit-test.
 
 ---