docs: 1.0 documentation restructure

Split root CLAUDE.md into 19 per-directory files scoped to their source area.
Roll v0 history into docs/ARCHIVE.md; retire CONTEXT.md, CONTEXT-ARCHIVE.md,
PLAN.md, COMPLETED.md. Move plan docs under docs/. Rescue 9 live deferrals
into docs/TODO.md.

docs/COMPLETED.md

@@ -0,0 +1,8 @@
+# COMPLETED.md — ReaSampler landed milestones
+
+Completed milestone entries removed from `PLAN.md`. Each entry preserves its
+original Goal, Verify, and checklist points with boxes marked done.
+
+This file holds the current (1.x) cycle's landed milestones only. Nothing has
+landed in the 1.x cycle yet. For all pre-1.0 (version-0) history, see
+`docs/ARCHIVE.md`.

docs/TODO.md

@@ -0,0 +1,133 @@
+# TODO
+
+Forward-looking follow-ups. Deferred by decision, not oversight — each entry records why it was deferred and what "done" looks like.
+
+## Persist ReaSampler 9000 instance identity to let prune reclaim de-referenced captures after reopen
+
+**Context (what shipped — Phase S usage-detection).** Each ReaSampler 9000 instance publishes the captures it holds to project ext-state (`rsusage_<guid>` keys, ComponentState v11). The extension's prune reads those records and unions every live instance's held captures into the referenced-set, so a capture any live instance holds can never be pruned. Fail-safe: unreadable/ambiguous usage state aborts prune (deletes nothing). Airtight on safety.
+
+**The wart.** The per-instance identity token is minted fresh each incarnation and is NOT persisted. After save→reopen, an instance cannot recognize its OWN prior-session usage record — it looks foreign, so the instance defensively unions and marks the record append-only (poisoned). Net effect: after any reopen, prune stops reclaiming captures an instance once loaded but no longer uses. Safe (never deletes a used capture), but the bank folder grows without bound.
+
+**Intended fix.** Persist the instance identity in ComponentState so an instance recognizes its own last-session record and does a clean-replace instead of union/poison → prune reclaims de-referenced instance-touched captures normally.
+
+**The constraint the fix MUST handle (why deferred).** VST3 provides no stable per-instance identity, and Ctrl+D / in-place FX duplication clones plugin state. A persisted identity is inherited by an in-place duplicate → two live instances in one project share one `rsusage_<guid>` key. Harmless while both hold the same capture; the risk is a divergent clone — the copies load DIFFERENT captures, and last-writer-wins drops the other's held capture from the record, exposing it to prune. The fix must detect a genuine live same-identity collision and protect the union in that case, WITHOUT reintroducing the sibling-drop bug the fresh-per-session token was originally added to prevent. (Whole-project copies are a non-issue — bank files are cloned with the project and ext-state is per-project.)
+
+**Priority / risk.** Low / deferred. Current behavior is safe; the only cost is unbounded bank-folder growth after reopens. Decided 2026-07-28 to ship the safe version and defer this.
+
+**Done looks like.** Save → reopen → de-reference a capture from an instance → prune reclaims it. And: in-place-duplicate + diverge + delete-from-bank never deletes a capture a live instance holds.
+
+## Isolate capture from out-of-scope aux/parallel sends, not just FX/gain/pan
+
+**Context (carried from PLAN.md's "Open questions to resolve during build").** The FX-scope capture neutralizes out-of-scope FX, gain, and pan for both item and track scope — root `CLAUDE.md`'s "Capture FX scope" precision invariant states this precisely: the out-of-scope chain (ancestors + master track, plus the item's own track for item scope) has its FX, gain, and pan/width/pan-law/mode neutralized to unity. **Aux/parallel sends are conspicuously absent from that enumerated list** — the invariant as currently written does not cover them, which is the gap this item exists to close.
+
+**The wart.** A downstream coloring send (e.g. a folder → reverb-track send) still routes and blends into an item/track capture, past the intended isolation point. Repro from PLAN.md: folder F1; T1 (MIDI) sends MIDI to T2 (synth); T1+T2 → F1; F1 sends to reverb T3; capturing the MIDI item on T1 currently includes the reverb, but should be isolated to T2's synth output pre-F1 with the MIDI send preserved and the reverb send excluded.
+
+**Intended fix.** Likely approach (PLAN.md): snapshot + mute out-of-scope tracks' aux sends during the render while preserving the main/source signal path.
+
+**The constraint the fix MUST handle.** Distinguish **source routing that must be preserved** (e.g. a MIDI send T1→T2 where T2's synth is where a MIDI item's audio is actually produced — the "item level" for that MIDI item is T2's synth output) from **coloring sends that must be excluded** (folder→reverb). PLAN.md notes this is "the hard part" and that a rule is needed for which sends are load-bearing.
+
+**Settled rule (Daniel, 2026-07-29).** The classification rule for which sends are load-bearing: (1) **ancestor sends are excluded** from the capture — the folder parent is *up* the folder tree but *downstream* in signal flow, so this item deliberately says "ancestor," not "upstream," which would read backwards to anyone applying signal-flow convention; (2) **sibling sends are preserved and captured** — a sibling is a track sharing the capture scope's parent; (3) **if the send's destination has a different parent, ignore it in the capture** — it isn't a sibling, so it isn't captured. Applied to the repro above: the T1→T2 MIDI send is a sibling send (T1 and T2 share parent F1) and is preserved — T2's synth is where the item's audio is actually produced; the F1→T3 reverb send is an ancestor send and is excluded. This resolves the repro.
+
+**Still open.** The rule above settles *which sends to mute*, but the repro is only fully resolved together with a second, unspecified lever — *where the capture taps*. PLAN.md's own framing of this open question says a true item-level capture should be taken "at the isolated graph point — the target scope's output before out-of-scope track FX/gain/pan and before out-of-scope aux/parallel sends." How the mute-rule above and the tap-point interact is not yet specified.
+
+**Priority / risk.** Not stated in PLAN.md (recorded there as an open `(TODO)` question, not yet triaged to a priority). Flagged here as mattering more than the other four carried-over items because it exposes a live gap in a stated precision invariant, not just a deferred feature.
+
+**Done looks like.** Capturing the MIDI item on T1 in the repro above is isolated to T2's synth output pre-F1 — the T1→T2 MIDI send is preserved and the F1→reverb send is excluded — and the CLAUDE.md "Capture FX scope" invariant's neutralization list is extended to name sends explicitly.
+
+## Confirm REAPER's VST3 UID-vs-filename instance rebind behavior (Phase S compat verification)
+
+**Context.** PLAN.md, under "Phase S — product name (ReaSampler 9000)": the working assumption is that REAPER rebinds a saved instance by its VST3 class UID, not by the module filename, so a filename rename with an unchanged UID keeps saved projects working (existing instances still resolve).
+
+**The wart.** This is not yet confirmed from source — PLAN.md records that a web check surfaced a JUCE/VST3-replace-VST2 case suggesting REAPER's binding is more nuanced than "UID only" (it can involve an FXID match), so UID-rebind is to-verify, not asserted fact.
+
+**Intended fix / required check.** DAW-verify: save a project with a ReaSampler 9000 instance under the old filename, rename the module, reopen — confirm the instance rebinds and restores its state.
+
+**The constraint the fix MUST handle.** If REAPER does key partly on filename, the fallback is to keep the current filename (display-strings-only) and record that as the shipped choice.
+
+**Priority / risk.** Marked "must-DAW-verify before shipping the rename" in PLAN.md; no explicit priority level stated beyond that.
+
+**Done looks like.** The save→rename→reopen DAW check is performed and its result (rebind confirmed, or filename-revert fallback taken) is recorded.
+
+## S13 — cross-artifact ingest relay (deferred, spike verdict DEGRADED)
+
+**Context.** PLAN.md records the ps-w12 (2026-07-27) spike verdict: DEGRADED — relay deferred. The instrument's REAPER bridge (`reaper_bridge`) is deliberately READ-ONLY; a relay would need a new instrument WRITE seam into ext-state and an extension-side timer poller servicing a drop-ingest inbox key with a claim/clear nonce — the same cross-process handshake race the S17 spec rejected for alternative (A). The shipped ingest gesture stays drop-onto-docked-panel (S8); the editor shows a "drop files onto the ReaSampler bank panel to add them" affordance as the degrade path.
+
+**The wart.** Dropping a file directly onto the editor/instrument does not ingest it into the bank — only drop-onto-docked-panel does.
+
+**Intended fix.** The editor hands the dropped path + this instance's identity to the extension as a bank-ingest request over an agreed seam.
+
+**The constraint the fix MUST handle.** Requires (a) a new instrument WRITE seam into ext-state (breaking the current read-only-bridge invariant) and (b) an extension-side timer poller + claim/clear nonce — both are load-bearing design calls that need to be made deliberately, not as a call-site patch. Both the read-only-instrument boundary and the new poller were judged load-bearing enough that the relay is deferred to a future wave rather than pushed through now.
+
+**Priority / risk.** PLAN.md marks this DEFERRED, awaiting a future wave, with no priority assigned.
+
+**Done looks like.** Not stated in PLAN.md beyond "a future wave when the design is ready."
+
+## Phase D2 — per-track lane/mode-state panel indicator (deferred)
+
+**Context.** PLAN.md: Phase D2 is functionally complete (D2-W1, D2-W2, D2-W3-A, D2-W3-B all landed). One item was deferred out of that completion: a panel UI indicator for per-track lane/mode state (a per-track lane-split marker).
+
+**The wart.** The mode switch already shows the active mode, but there is no per-track indicator; PLAN.md records that no natural cheap home for one was found in the bank panel.
+
+**Intended fix.** Not specified in PLAN.md beyond the goal (a per-track lane-split marker in the bank panel) — the design is unresolved, which is part of why it was deferred rather than built.
+
+**The constraint the fix MUST handle.** Finding a home for the indicator in the bank panel's existing layout, which PLAN.md notes doesn't currently have a natural cheap spot for it.
+
+**Priority / risk.** Not stated in PLAN.md. PLAN.md's own framing: "Explicitly deferred — not silently dropped. Can be picked up later if wanted."
+
+**Done looks like.** Not stated in PLAN.md.
+
+## FX-GUID keying for `restoreFxOffline` (Design View park/restore)
+
+**Context.** CONTEXT.md's "Open questions to resolve during build" (Design View section): the bulk of reconcile residuals shipped (`ViewModeModel::reconcile(liveGuids)` prunes orphaned snapshots on every toggle/load; folder restructure is self-healing because the tree is rebuilt each toggle; membership is intentionally kept so undo-delete preserves the tag). Two sub-items were left deferred out of that; this is the first.
+
+**The wart.** `restoreFxOffline` currently restores per-FX offline state by slot index. If the FX chain is reshuffled while a track is parked, restore lands on whatever plugin now occupies that slot rather than the plugin it was originally captured from.
+
+**Intended fix.** FX-GUID keying — key the per-FX offline snapshot entries by FX identity rather than slot index.
+
+**The constraint the fix MUST handle.** The keying change requires a snapshot-schema migration; CONTEXT.md names this alongside the keying change as the reason the fix was deferred rather than folded into the reconcile-residuals work.
+
+**Priority / risk.** Not stated in the source.
+
+**Done looks like.** Not stated in the source beyond the fix description above.
+
+## Dormant membership entries in persisted `view_state`
+
+**Context.** CONTEXT.md's "Open questions to resolve during build" (Design View section), the second of the two sub-items left deferred after the reconcile-residuals ship described above.
+
+**The wart.** Truly-deleted tracks accumulate stale entries in persisted `view_state`.
+
+**Intended fix.** A future user-initiated "compact" action to remove the stale entries.
+
+**The constraint the fix MUST handle.** Must NOT be automatic pruning — automatic pruning would reintroduce the undo-delete tag-loss that the deliberate membership-retention was designed to prevent.
+
+**Priority / risk.** Not stated as a priority level; the source characterizes the wart itself as "harmless and bounded."
+
+**Done looks like.** Not stated in the source beyond "a future user-initiated 'compact' action."
+
+## Confirm no fight between Design View flags and screenset recall
+
+**Context.** CONTEXT.md's "Open questions to resolve during build" (Design View section): Design View drives the same track flags a screenset recall would drive, and last writer wins between the two.
+
+**The wart.** Not a defect — this is a verification task, not a code change. The open concern is confirming there is no surprising interaction between Design View's flag-driving and an active screenset recall.
+
+**Intended fix.** N/A — no fix is proposed; the task is to confirm no surprising fight between the two mechanisms.
+
+**The constraint the fix MUST handle.** N/A — verification only.
+
+**Priority / risk.** Not stated in the source.
+
+**Done looks like.** Not stated in the source beyond "confirm no surprising fight."
+
+## Active-bank indicator placement (B4 polish)
+
+**Context.** CONTEXT-ARCHIVE.md's "Open questions to resolve during build" (B4 panel section): forks 1–5 are all settled; one panel-polish detail remains open. Fork 4 already settled that the active-bank indicator must be "visually unmistakable" — only its placement is undecided.
+
+**The wart.** No placement chosen yet among three candidates: per-region headers, a single header readout, or a lit-tab treatment.
+
+**Intended fix.** Not stated in the source beyond the three candidate placements above — the choice among them is the open item. This is explicitly a panel-polish detail.
+
+**The constraint the fix MUST handle.** Not stated in the source.
+
+**Priority / risk.** Not stated as a priority level; the source characterizes this as a "panel-polish detail."
+
+**Done looks like.** Not stated in the source beyond choosing one of the three placement options.

docs/product/audit-notes/q-w0-t2-architecture.md

@@ -10,7 +10,8 @@ flatness, naming families) are **not restated**; where a finding below touches t
 is because the functional mechanism is new.
 
 Every claim below was verified by grep/read of the actual tree. Line numbers are as of this
-audit's snapshot. Wave assignments reference PLAN.md §Q-W1..Q-W6.
+audit's snapshot. Wave assignments reference the Q-W1..Q-W6 waves (landed history in
+`docs/ARCHIVE.md`; sequencing in `docs/product/code-organization.md` §5).
 
 ---
 

docs/product/audit-notes/q-w0-t3-env-constants.md

@@ -2,9 +2,9 @@
 
 Static analysis, 2026-07-28, branch `pq-w0-audit`. Scope: any value stored in an
 environment-coupled domain — frames, sample rate, DPI, pixels, tick cadence — that should be
-stored **rate-free / device-free and resolved at the point of use** (PLAN.md §Q-W0 env-coupled
-bullet; `docs/product/code-organization.md` §2c.3; the load-bearing `sample_map` seconds
-invariant). Findings are domain-modeling calls, not "rescale by rate" patches. The judgment bar
+stored **rate-free / device-free and resolved at the point of use** (`docs/product/code-organization.md`
+§2c.3 env-coupled bullet; the load-bearing `sample_map` seconds invariant, documented in
+`src/core/instrument/CLAUDE.md`). Findings are domain-modeling calls, not "rescale by rate" patches. The judgment bar
 applied: a finding requires (a) an env-coupled *stored* domain AND (b) an environment that can
 actually change under it. Frame counts computed transiently from seconds at the use site are
 correct and are not reported.
@@ -63,7 +63,7 @@ fix-now findings in those files must be remediated in Q-W0 itself.
   normalize the Trigger fade-in/out knobs.
 - **Stored vs. correct domain:** the fade **storage** domain (int64 SOURCE frames, persisted in
   the zones payload) is settled and correct — a source-timeline fact, invariant under project-
-  rate change (PLAN.md §S15). The *UI ceiling*, however, encodes a wall-clock intent ("2-second
+  rate change (`docs/ARCHIVE.md` §S15). The *UI ceiling*, however, encodes a wall-clock intent ("2-second
   max fade throw") as a frame count at an assumed 44.1 kHz source. `88200` is a rate-derived
   literal in `src/`, brushing the no-hardcoded-rate ruling even though it never touches disk.
 - **What breaks when the environment shifts:** the environment here is the **source file's
@@ -165,7 +165,7 @@ fix-now findings in those files must be remediated in Q-W0 itself.
   `SampleRefs` (paths + root/loop/channels intrinsics), `instanceGuid` — all rate-free or
   file-fact domains. Clean.
 - **Trigger `fadeInFrames`/`fadeOutFrames`/`startPoint`/`SampleLoop.start/end` persisted as
-  int64 SOURCE frames:** deliberate, settled source-timeline facts (PLAN.md §S15;
+  int64 SOURCE frames:** deliberate, settled source-timeline facts (`docs/ARCHIVE.md` §S15;
   `bank_model.h:66-72` documents the loop rationale) — frames *of the file* are invariant under
   project-rate change; the file's own rate is stored alongside and resolved at decode. Correct
   domain, not a finding.

docs/product/capture-tail.md

@@ -1,19 +1,20 @@
 # Capture tail — spec
 
 Authoritative spec for the **capture-tail** feature: preserving reverb/release
-tails that decay past the end of a capture range. The tickable milestone lives in
-`PLAN.md` (Milestone T); this doc holds the full technical detail **and** the
-product framing.
+tails that decay past the end of a capture range. The tickable milestone's landed
+history is in `docs/ARCHIVE.md` (Milestone T); this doc holds the full technical
+detail **and** the product framing.
 
-> **Why this doc carries the technical spec (not `CONTEXT.md`).** Every other
-> pillar (capture M0–M11, Design View, Multi-bank) keeps its authoritative
-> technical spec as a `CONTEXT.md §` section and its *why* in a `docs/product/`
-> note. Capture-tail is a rider on the already-shipped offline-render path
-> (M3/M7), not a standalone pillar, and it is being specced without reopening
-> `CONTEXT.md`. So the authoritative detail lands **here**, house-styled to match
-> the CONTEXT specs; when the tail work lands, doc-keeper may fold the invariant
-> deltas into `CONTEXT.md §Precision invariants` as landed history. Same standing
-> discipline applies: **verify every REAPER API name/flag against
+> **Why this doc carries the technical spec (not the architecture docs).** Every
+> other pillar (capture M0–M11, Design View, Multi-bank) keeps its authoritative
+> technical spec as a per-directory `src/**/CLAUDE.md` section and its *why* in a
+> `docs/product/` note. Capture-tail is a rider on the already-shipped
+> offline-render path (M3/M7), not a standalone pillar, and it was specced without
+> reopening the architecture spec. So the authoritative detail lands **here**,
+> house-styled to match those specs; the landed invariant deltas are folded into
+> root `CLAUDE.md` §Precision invariants and `src/core/capture/CLAUDE.md` /
+> `src/shell/capture/CLAUDE.md` as landed history. Same standing discipline
+> applies: **verify every REAPER API name/flag against
 > `vendor/reaper-sdk/sdk/reaper_plugin_functions.h` before use** — the flag values
 > below are transcribed from that header (line numbers cited) and are not guesses.
 
@@ -252,7 +253,7 @@ held to bit-identical repeats.
 - **Opt-in beyond the region.** The tail only ever adds audio past the range end
   when a tail is explicitly requested (Auto or Manual). This is exactly the existing
   invariant: *"no added silence unless a tail is explicitly requested"*
-  (`CONTEXT.md §Precision invariants`, `CLAUDE.md §Exact bounds`). Auto-trim
+  (`CLAUDE.md §Precision invariants §Exact bounds`). Auto-trim
   strengthens it — the tail added is decay, not silence, and the silence past the
   decay is trimmed off.
 - **The null test uses NO tail.** The null-test / verify capture (M10) and any
@@ -274,8 +275,8 @@ held to bit-identical repeats.
     the tail is **the track's own reverb/delay decay**, not the parent bus's. A track
     with a reverb plugin captures that reverb's tail; a track feeding a folder reverb
     does **not** capture the folder reverb's tail (that send is out of scope — and
-    note the pre-existing send-isolation caveat in `PLAN.md §Open questions`, which
-    the tail inherits unchanged, does not worsen). Correct and consistent.
+    note the pre-existing send-isolation caveat, which the tail inherits
+    unchanged, does not worsen). Correct and consistent.
   - **Item scope:** item/take FX only, self-track + ancestors + master bypassed →
     the tail is the **item/take FX decay only**. An item with a take reverb captures
     its tail; the track's reverb does not ring into it. Correct.

docs/product/code-organization.md

@@ -9,8 +9,10 @@ subdirectories) **without sacrificing runtime performance**, against a stated qu
 >
 > Bring the codebase "**into the realm of something I can stand to look at.**"
 
-Its build roadmap lives in **PLAN.md §Phase Q** and its authoritative spec in
-**CONTEXT.md §Phase Q**. This doc holds the *why* — the quality bar, the evidence base
+Its build roadmap's landed history lives in **`docs/ARCHIVE.md`** ("Phase Q — Quality:
+the decision record") and its authoritative spec now lives in root **`CLAUDE.md`**
+(§Directory and namespace layout, §Performance guardrails, §Structural heuristics)
+plus the per-directory `src/**/CLAUDE.md` files. This doc holds the *why* — the quality bar, the evidence base
 (a grep-verified SOLID audit), the target directory/namespace shape grounded in the Vital
 reference, and the numbered fork decisions.
 
@@ -321,10 +323,10 @@ re-namespaced, and split, not carried forward untouched into a tidier tree. "Som
 look at" is partly shape (§2/§2b) and partly *functional soundness* (§2c).
 
 Q-W0 is **not executed by product-designer** — this doc *defines the wave and its scope*; the audit
-itself is staff-engineer/DSP work. The authoritative wave definition lives in **PLAN.md §Q-W0** and
-its spec framing in **CONTEXT.md §"The pre-restructure audit wave (Q-W0)"**; this section is the
-evidence-doc framing (the *why* and the smell taxonomy), matching how §2/§2b frame the structural
-audits.
+itself is staff-engineer/DSP work. The wave's landed history lives in **`docs/ARCHIVE.md`**
+("Q-W0 fix-now remediations" and "Phase Q — Quality: the decision record"), and its findings live in
+**`docs/product/code-quality-audit.md`**; this section is the evidence-doc framing (the *why* and
+the smell taxonomy), matching how §2/§2b frame the structural audits.
 
 ### 2c.1 Audit surfaces (the named targets)
 
@@ -451,7 +453,7 @@ namespace of every header, splitting the four largest TUs). Meanwhile:
 - **Phase L** has **L3** (VST editor + embed-strip restyle, gated on Phase S landing on dev)
   still to land — it touches the Phase S draw shells (`reasampler_editor` / `reasampler_embed`),
   which arrive on dev with Phase S. (L1/L2/L4/L5/L6/L7 have **already landed** — see
-  `COMPLETED.md`; the once-listed "L2 pending" is stale and has been corrected here.)
+  `docs/ARCHIVE.md`; the once-listed "L2 pending" is stale and has been corrected here.)
 - **D2** is **functionally complete** (D2-W1..W3-B landed; the only open item — a per-track
   lane-split panel indicator — is *explicitly deferred*, not a blocking residual). **M9** (slots)
   is **abandoned** (Daniel, 2026-07-27) — will not be built. D2 is named in the gate only so a

docs/product/code-quality-audit.md

@@ -3,7 +3,8 @@
 Date: 2026-07-28 · Branch: `pq-w0-audit` · Static analysis only; no code changed by the audit.
 
 This is the committed Q-W0 findings report (Q-10 SETTLED: a committed doc beside the SOLID/naming
-audit — `docs/product/code-organization.md` §2c.3; deliverable contract in PLAN.md §Q-W0). It
+audit — `docs/product/code-organization.md` §2c.3; deliverable contract landed per `docs/ARCHIVE.md`
+§Phase Q). It
 synthesizes four parallel audit tracks; the full track notes remain in the tree as appendices and
 are the evidence base for every claim here — this report cites finding IDs and does not restate
 mechanisms in full:

docs/product/design-view.md

@@ -1,8 +1,9 @@
 # Design View — product notes
 
 Framing, rationale, and design-direction calls behind the **Design View** phase.
-The tickable spec lives in `PLAN.md` (Phase D) and the authoritative technical
-detail in `CONTEXT.md` (§Design View). This doc holds the *why* — the workflow
+The tickable spec's landed history lives in `docs/ARCHIVE.md` (Phase D) and the
+architecture detail in `src/core/view/CLAUDE.md` + `src/shell/view/CLAUDE.md`
+(§Design View). This doc holds the *why* — the workflow
 narrative, the N-mode reasoning, the screenset differentiation, and the
 design-direction recommendations — so those don't clutter the build docs.
 
@@ -339,8 +340,7 @@ tooltip on the switch.
    `docs/design/`), say so and it moves. Flagging because establishing the
    directory is a project convention, not mine to assume silently.
 2. **Phase namespace.** Proposed **Phase D** (a lettered namespace) rather than
-   M12 — see PLAN.md rationale. Confirm you're happy with letters for parallel,
-   non-capture phases.
+   M12. Confirm you're happy with letters for parallel, non-capture phases.
 3. **SDK name correction.** The brief cited `B_SHOWINMCP`; the verified SDK flag
    for mixer-panel visibility is **`B_SHOWINMIXER`** (SDK header line 2235). The
    spec uses the verified name. Just flagging the discrepancy so it isn't a

docs/product/midi-playback.md

@@ -2,10 +2,11 @@
 
 Framing for a **MIDI-triggered audio sampler** that plays back ReaSampler's captured
 banks. This began as a discussion-shaping doc; with all forks now settled it has become
-the **product framing behind a scoped phase**. Its build roadmap lives in **PLAN.md
-§Phase S** and its authoritative spec in **CONTEXT.md §Phase S** — this doc holds the
-*why* (the plugin-format reasoning, the bare-VST3-vs-JUCE assessment, the settled
-decision record).
+the **product framing behind a scoped phase**. Its build roadmap lives in
+**`docs/ARCHIVE.md` §Phase S** and its authoritative spec in
+**`src/core/instrument/CLAUDE.md`** and **`src/shell/instrument/CLAUDE.md`** — this
+doc holds the *why* (the plugin-format reasoning, the bare-VST3-vs-JUCE assessment, the
+settled decision record).
 
 Status: framed by product-designer (2026-07-26), **revised 2026-07-27 (r11)**. r11 records the
 **Sample-face recomposition** (Daniel's post-landing DAW pass, 2026-07-27): all linear sliders →
@@ -42,10 +43,11 @@ demoted to an opt-in Zones panel — see the r6 Addendum in §4. r6 also settles
 S1–S6 instrument: the product name **ReaSampler 9000** and the **"better than RS5K" UX
 overhaul** (Phase S points S10–S13) — see the r5 Addendum in §4. r4 (below) settled the four
 residual forks D-A..D-D. The
-"no PLAN.md footprint" era is **over** — with D-A through D-D settled (below), the
+"no landed-roadmap footprint" era is **over** — with D-A through D-D settled (below), the
 instrument was scoped into **Phase S** (codename Daniel's: "S" for Sampler, because "D"
-collides with the existing Design View phase). **PLAN.md §Phase S is now the
-authoritative roadmap; CONTEXT.md §Phase S is the authoritative spec.** This doc is the
+collides with the existing Design View phase). **`docs/ARCHIVE.md` §Phase S now records
+the landed roadmap; `src/core/instrument/CLAUDE.md` and `src/shell/instrument/CLAUDE.md`
+are the authoritative spec.** This doc is the
 framing/decision record they point back to. Prior revisions (a) established that a REAPER
 *extension* cannot be a MIDI instrument, (b) corrected a material omission — REAPER's
 **VST-host bridge**, which lets a VST3 plugin *hosted inside REAPER* call back into
@@ -410,8 +412,8 @@ it doesn't carry" — is unchanged. What the bridge settles is *where that mappi
 between extension and instrument as **live shared `"reasampler"` state**, not a file one
 writes and the other re-parses.
 
-**What the current index carries** (from `bank_model`'s `Sample`, per CONTEXT.md §Data
-model): id, display name, relative path, source range, channel count, sample rate,
+**What the current index carries** (from `bank_model`'s `Sample`): id, display name,
+relative path, source range, channel count, sample rate,
 length, capture tempo, an **optional key**, peak/RMS/LUFS, content hash, tier,
 provenance, timestamp. Notably it *already* has an optional key field and capture
 tempo — the seeds of pitch-mapping are there.
@@ -426,8 +428,8 @@ tempo — the seeds of pitch-mapping are there.
   to velocity zones).
 - **Round-robin groups** (cycle through N samples on repeated same-note hits).
 - **Loop points** (sustain loop start/end for held notes; sample-accurate,
-  zero-crossing-aware — CONTEXT already flags loop/zero-crossing handling as
-  day-one-relevant for wavetable material).
+  zero-crossing-aware — loop/zero-crossing handling is day-one-relevant for
+  wavetable material).
 - **Amplitude envelope** (ADSR) and optionally filter/pitch envelopes.
 - **Tuning/gain trim** per sample.
 
@@ -559,7 +561,7 @@ ReaSampler-native way to build it and it's assumed, not debated, going forward.
 
 All four residual decisions are now called. Each is marked **SETTLED** with Daniel's
 choice and the reasoning kept as the record of *why* — do not re-litigate. They are
-scoped into **PLAN.md §Phase S** / **CONTEXT.md §Phase S**.
+scoped into **`docs/ARCHIVE.md` §Phase S** / **`src/core/instrument/CLAUDE.md`**.
 
 **D-A — SETTLED: bare Steinberg VST3 SDK + LICE editor (no JUCE).** *(The central fork.
 §1a is the assessment that fed it. The sub-question — who draws the editor? — was the
@@ -649,7 +651,7 @@ After Phase S was scoped (D-A..D-D), Daniel set two further directions. These ar
 **settled directions**, not open forks — specced as new Phase S points (S7–S9), not
 re-litigated. Recorded here per the doc's settled-decisions convention.
 
-**D-E — Channel mode: mono | stereo, per-instance, bus-negotiated (→ PLAN.md S7).**
+**D-E — Channel mode: mono | stereo, per-instance, bus-negotiated (→ `docs/ARCHIVE.md` §S7).**
 Captures are often stereo; the current mono downmix is a Tier-0 simplification. The
 engine gets a **per-instance channel-mode toggle (1 mono / 2 stereo)** that "works with
 the REAPER audio bus automatically" — the VST3 declares/negotiates its output bus
@@ -662,8 +664,8 @@ Cross-mode policy: mono-source-in-stereo → dual-mono; stereo-source-in-mono
 never a bank fact). Sequenced **first after the editor/embed work** because it touches the
 engine Daniel smoke-tests.
 
-**Ingest routes through the bank — "option 1"; the extension owns ingest (→ PLAN.md
-S8 + S9).** Loading a sample into the sampler is **one gesture**: capture/import-into-bank
+**Ingest routes through the bank — "option 1"; the extension owns ingest (→
+`docs/ARCHIVE.md` §S8 + §S9).** Loading a sample into the sampler is **one gesture**: capture/import-into-bank
 + auto-assign to the active instance. The **extension owns ingest** (it has arrange
 access, Media-Explorer access, and the drop-target surface on its own panels); the
 **instrument stays a read-only bank consumer** — it never captures or imports. Sub-parts,
@@ -690,7 +692,7 @@ with the honest SDK reality verified against the vendored headers:
 
 *The genuine spikes flagged (not decisions Daniel owes, just build-time unknowns):* the
 ME merely-selected-file read (b), and the drop-onto-editor cross-artifact relay (c). Both
-are honestly-flagged as spikes in PLAN.md S8, not promised.
+are honestly-flagged as spikes in `docs/ARCHIVE.md` §S8, not promised.
 
 ### Addendum — product name + UX overhaul (Daniel, 2026-07-26, post-S1–S6 DAW test)
 
@@ -700,7 +702,7 @@ open forks (the two flagged forks below are the only calls left to Daniel).
 
 **The instrument's product name is `ReaSampler 9000`.** The extension stays **ReaSampler**
 (capture + organization); the instrument is **ReaSampler 9000** (playback). Propagation is
-a checklist item (PLAN.md §Phase S — product name; CONTEXT.md §Product name): the VST3
+recorded in `docs/ARCHIVE.md` §Phase S — product name: the VST3
 class **display name** string, the `IPlugView` editor title band (today "ReaSampler
 Instrument"), the S6 embed-strip label, and the docs. **Compat guard (load-bearing):** the
 **VST3 class UID must NOT change** — instances in saved projects key off it; a UID change
@@ -747,8 +749,9 @@ names the editor as the wound.
 
 After the r5 UX-overhaul directive was specced (keymap-first S10), Daniel reframed the
 workflow before S10 was implemented. This **revises S10** and settles S-NAME-1. Settled
-directions, not open forks — recorded here per the doc's settled-decisions convention; PLAN.md
-§S10 and CONTEXT.md §Phase S (workflow hierarchy) carry the spec.
+directions, not open forks — recorded here per the doc's settled-decisions convention;
+`docs/ARCHIVE.md` §S10 records what landed and `src/core/instrument/CLAUDE.md` (the
+editor `ui/` modules) documents the current architecture.
 
 **The reframe, verbatim (Daniel, 2026-07-26):** *"We need to think hard about the workflow
 with this plugin. Have a giant list of 'item' blocks is visually useless. When the plugin is
@@ -806,8 +809,8 @@ partly on filename, fall back to keeping the filename and record that as shipped
 
 Daniel directed a set of engine features for the sampler, specced as **new Phase S points
 S15 (Trigger vs Gate) and S16 (pitch envelope)**. **The feature set is settled** — recorded
-here per the doc's settled-decisions convention; PLAN.md §S15/S16 and CONTEXT.md §Sampling
-modes carry the spec. Two forks are flagged with leans (S15-F1 choke, S15-F2 param
+here per the doc's settled-decisions convention; `docs/ARCHIVE.md` §S15 / §S16 records what
+landed and `src/core/instrument/CLAUDE.md` §Sampling modes documents the current spec. Two forks are flagged with leans (S15-F1 choke, S15-F2 param
 granularity); the WDL question was resolved by inspection.
 
 **Directive, verbatim (Daniel, 2026-07-26):** *"let's have product spec out some features
@@ -927,9 +930,10 @@ This reshapes S16 and **flips the r7 WDL verdict** on `WDL_SimplePitchShifter`.
    `process` allocation; measure per-voice CPU + onset latency against the polyphony cap. Treat
    S16's Preserve-engine point as the phase's next real DSP spike, not a thin envelope add-on.
 
-**Where the spec lives:** PLAN.md §S16 (reshaped to "pitch engine modes + pitch envelope",
-with forks S16-F1/F2 and the corrected WDL finding) and the S15 × S16 interaction note;
-CONTEXT.md §Pitch engine modes — Varispeed vs Preserve + the corrected WDL surface finding.
+**Where the spec lives:** `docs/ARCHIVE.md` §S16 (reshaped to "pitch engine modes + pitch
+envelope", with forks S16-F1/F2 and the corrected WDL finding) and the S15 × S16
+interaction note; `src/core/instrument/CLAUDE.md` §Sampling modes — Varispeed vs Preserve
++ the WDL surface finding.
 
 ### Addendum — VST channel isolation (Daniel, 2026-07-26)
 
@@ -972,9 +976,9 @@ with or right after the in-flight waves (S9 ext_keys, S15/S16 processor/editor)
    channel's banks; stable-project + beta-VST = clean empty (not error); the S-NAME-1
    rename/rebind test extends to the beta UID.
 
-**Where the spec lives:** PLAN.md §S18; CONTEXT.md §VST3 channel identity — the UID pair + the
-pairing surface. The pairing surface's data half is already load-bearing V4 machinery; S18
-adds only the identity fork on top.
+**Where the spec lives:** `docs/ARCHIVE.md` §S18; `src/shell/instrument/CLAUDE.md` §VST3
+channel identity — the UID pair + the pairing surface. The pairing surface's data half is
+already load-bearing V4 machinery; S18 adds only the identity fork on top.
 
 ---
 
@@ -986,8 +990,9 @@ good — but the two-view editor (today's "Browser" + "Zones" toggle) misallocat
 the default window is undersized for a 1080p world, and the drop-a-capture-onto-FX gesture is
 broken in practice. The directive: **make the one job — pick a capture, tune it, play it —
 fast, easy, and fun. Style is a critical ingredient. No spreadsheet aesthetics.** These are the
-`r9` calls. Authoritative spec: **CONTEXT.md §Phase S — editor view-model redesign (S-VIEW)**;
-build roadmap: **PLAN.md §Phase S — editor view-model redesign**.
+`r9` calls. Current architecture: **`src/core/instrument/CLAUDE.md`** and
+**`src/shell/instrument/CLAUDE.md`**; landed record: **`docs/ARCHIVE.md` §Phase S — editor
+view-model redesign**.
 
 **The reference devices (the north star for control density).** Daniel named Ableton **Simpler**
 and a Kilohearts/Phase-Plant **sampler group** as the composition targets. Both share one
@@ -1021,7 +1026,7 @@ grammar, and it is the grammar the redesign adopts:
    loading a new one is a distinct act), not a three-way radio. *Why the reframe matters:* it
    makes "I just want to play this capture" the zero-click default, and "I want a different one"
    a single deliberate gesture, instead of making the user re-choose their whole stance every
-   time. See CONTEXT.md §S-VIEW for the precise navigation model.
+   time. See `docs/ARCHIVE.md` §S-VIEW-1 for the precise navigation model as landed.
 
 2. **The Sample view earns the hero treatment; Browse gets ruthlessly cut.** Browse today
    carries a waveform preview, root-note piano-roll, loop-point labels, a track-root message, and
@@ -1037,10 +1042,10 @@ grammar, and it is the grammar the redesign adopts:
 3. **Two engineering prerequisites, framed but routed to implementation.** The **drop-to-FX bug**
    (dropping a capture onto a track's FX chain does not instantiate + init ReaSampler 9000) and
    the **undersized default window** are not design decisions — they are a bug and a one-line
-   default. Both are framed in CONTEXT.md §S-VIEW with the SDK reality swept (drop-to-FX: the S17
-   machinery is SDK-correct, so this is a *diagnosis* task, not a redesign; window size: the
-   `getSize`/`checkSizeConstraint` mechanism is verified), and both are flagged for
-   staff-engineer, not for a product fork.
+   default. Both are recorded landed in `docs/ARCHIVE.md` §S-VIEW-BUG-1 (drop-to-FX: the S17
+   machinery is SDK-correct, so this is a *diagnosis* task, not a redesign) and §S-VIEW-SIZE-1
+   (window size: the `getSize`/`checkSizeConstraint` mechanism is verified), and both were
+   flagged for staff-engineer, not for a product fork.
 
 **New parameters this introduces (both instrument performance state, D-B — never bank facts):**
 
@@ -1064,7 +1069,7 @@ grammar, and it is the grammar the redesign adopts:
   new top-level `previewVelocity` field), **not** the extension's `persist` project ext-state —
   that module is REAPER-project-scoped and extension-owned, so it would make the level
   project-global instead of per-instance and route an instrument concern through a bank-read-only
-  seam. See CONTEXT.md §S-VIEW for the round-trip and back-compat lift. This is what makes the
+  seam. See `docs/ARCHIVE.md` §S-VIEW-4 for the round-trip and back-compat lift as landed. This is what makes the
   preview button *fun*: tap it hard or soft without reaching for a controller — and it remembers.
 
 **Two visual components the redesign commits to:**
@@ -1101,8 +1106,10 @@ persisted fields is not a compat event; saved instances rebind and restore. And
 (extended additively — `keyTrack` per-zone, `previewVelocity` per-instance via an envelope bump to
 v6, both with back-compat defaults on read) are the same load-bearing core.
 
-**Where the spec lives:** CONTEXT.md §Phase S — editor view-model redesign (S-VIEW); PLAN.md
-§Phase S — editor view-model redesign. This Addendum is the *why*; those are the *what/how*.
+**Where the spec lives:** `src/core/instrument/CLAUDE.md` (envelope overlay, key-tracking,
+preview-velocity ownership) documents the current architecture; `docs/ARCHIVE.md` §Phase S
+— editor view-model redesign records what landed (S-VIEW-1 through S-VIEW-10). This
+Addendum is the *why*; those are the *what/how*.
 
 ---
 
@@ -1217,8 +1224,9 @@ for preview velocity — a different struct on a different version axis). Concre
   the L1 kit, routing mouse through `velocity_curve`), gated on the foundation track and composing
   with the S-VIEW-2 Sample face + S-VIEW-3 envelope-overlay work.
 
-**Where the spec lives:** CONTEXT.md §Phase S — editor view-model redesign (S-VIEW), velocity-curve
-sub-section; PLAN.md §Phase S — editor view-model redesign (S-VIEW-9/S-VIEW-10 + fork R10-F1). This
+**Where the spec lives:** `src/core/instrument/CLAUDE.md` (the `velocity_curve` module, its
+engine application point, and its ownership rules) documents the current architecture;
+`docs/ARCHIVE.md` §S-VIEW-9 / §S-VIEW-10 records what landed (fork R10-F1 resolved). This
 Addendum is the *why*; those are the *what/how*.
 
 ---
@@ -1278,11 +1286,13 @@ recomposition of *existing* controls; no new params, no component-state bump, VS
 unchanged. All drawing through the L1 kit by palette role; all layout/hit-test in new pure modules
 (`knob_deck`, `curve_popup` — mirrors of `action_bar`/`overflow_menu`); the knobs and the hero's
 envelope nodes remain two surfaces on one param model (S-VIEW-F2's structural sync, untouched).
-The full inventory contract (every landed element → its r11 home) is in the CONTEXT.md spec.
+The full inventory of what landed (every element → its r11 home) is recorded in
+`docs/ARCHIVE.md` §FB1 and §FB2.
 
-**Where the spec lives:** CONTEXT.md §Phase S — editor view-model redesign (S-VIEW) → "The
-Sample-face recomposition (r11)"; PLAN.md §Phase S — editor Wave B (S-VIEW-11/12/13 + forks
-R11-F1/R11-F2). This Addendum is the *why*; those are the *what/how*.
+**Where the spec lives:** `src/core/instrument/CLAUDE.md` (the `knob_deck`/`curve_popup`/
+`master_gain` modules) documents the current architecture; `docs/ARCHIVE.md` §FB1 and §FB2
+record what landed (S-VIEW-11/12/13 + forks R11-F1/R11-F2 resolved). This Addendum is the
+*why*; those are the *what/how*.
 
 ---
 
@@ -1329,7 +1339,8 @@ Post-DAW-test directives (2026-07-26; see the "product name + UX overhaul" Adden
    frameworks), DS-2 (Direction B "Neon Console" + Direction C's spectral keyboard strip), and
    DS-3 (thorough panel layout) are all **SETTLED (2026-07-26)**. Framing + palette + the three
    visual directions + forks: `docs/product/visual-design-language.md` (on `dev`); roadmap +
-   spec: **PLAN.md §Phase L + CONTEXT.md §Phase L** (on `dev`). **S10–S13 build with the
+   spec: **`docs/ARCHIVE.md` §Phase L** (landed record) and **`src/core/ui/CLAUDE.md`**
+   (current architecture) (on `dev`). **S10–S13 build with the
    current drawing and adopt the L1 kit when it lands — not gated on Phase L.** Answers
    Daniel's "the VST is dogshit / temple os / does Cockos have a toolkit" (2026-07-26,
    post-S1–S6 DAW test).
@@ -1350,15 +1361,16 @@ Post-DAW-test directives (2026-07-26; see the "product name + UX overhaul" Adden
     S15-F1 (choke, held) / S15-F2 (param granularity, lean per-zone). Feature set settled;
     the engine default is Daniel's fork.
 
-**Authoritative from here:** **PLAN.md §Phase S** is the roadmap (S1–S6 the original
-dependency chain: spike → `Sample` fields → pure sampler core → Tier 0 → Tier 1 → embedded
-UI; then **S7** stereo, **S8** ingest, **S9** change-detection, **S10–S13** the ReaSampler
-9000 UX overhaul, **S15/S16** the Trigger-vs-Gate + pitch-engine-modes engine features);
-**CONTEXT.md §Phase S** is the spec (seam-field semantics, scope contracts, the channel-mode
-/ ingest / bank-generation / sampling-mode / pitch-engine contracts, the UX-overhaul spec,
-the product-name convention, the pure/shell split, the WDL finding, the must-verify
-SDK/bridge surfaces). This doc is the framing/decision record they point back to. The "no
-PLAN.md footprint" era is over.
+**Authoritative from here:** **`docs/ARCHIVE.md` §Phase S** is the landed roadmap (S1–S6
+the original dependency chain: spike → `Sample` fields → pure sampler core → Tier 0 → Tier
+1 → embedded UI; then **S7** stereo, **S8** ingest, **S9** change-detection, **S10–S13** the
+ReaSampler 9000 UX overhaul, **S15/S16** the Trigger-vs-Gate + pitch-engine-modes engine
+features); **`src/core/instrument/CLAUDE.md`**, **`src/shell/instrument/CLAUDE.md`**, and
+**`src/core/wire/CLAUDE.md`** are the current spec (seam-field semantics, scope contracts,
+the channel-mode / ingest / bank-generation / sampling-mode / pitch-engine contracts, the
+UX-overhaul spec, the product-name convention, the pure/shell split, the WDL finding, the
+must-verify SDK/bridge surfaces). This doc is the framing/decision record they point back
+to. The "no landed-roadmap footprint" era is over.
 
 ---
 

docs/product/multi-bank.md

@@ -1,8 +1,9 @@
 # Multi-bank — product notes
 
 Framing, rationale, and design-direction calls behind the **Multi-bank** phase.
-The tickable spec lives in `PLAN.md` (Phase B) and the authoritative technical
-detail in `CONTEXT.md` (§Multi-bank). This doc holds the *why* — the workflow
+The tickable spec's landed history lives in `docs/ARCHIVE.md` (Phase B) and the
+architecture detail in `src/core/model/CLAUDE.md` + `src/shell/bank_ops/CLAUDE.md`
+(§Multi-bank). This doc holds the *why* — the workflow
 narrative, the pool-privilege reasoning, the movement semantics, and the
 design-direction recommendations — so those don't clutter the build docs.
 

docs/product/provenance.md

@@ -1,10 +1,10 @@
 # Provenance — product notes
 
 Framing, rationale, and the dual-canvas reconciliation behind the reshaped
-**Milestone 10 (provenance)**. The tickable spec lives in `PLAN.md` (M10); the
-authoritative technical detail is `CONTEXT.md` (§Data model, §capture) plus this
-note for the reconciliation calls. This doc holds the *why* and the open forks so
-they don't clutter the build docs.
+**Milestone 10 (provenance)**. The tickable spec's landed history is in
+`docs/ARCHIVE.md` (M10); the architecture detail is in `src/core/model/CLAUDE.md`
+and `src/shell/capture/CLAUDE.md` plus this note for the reconciliation calls.
+This doc holds the *why* and the open forks so they don't clutter the build docs.
 
 Status: **IMPLEMENTED (2026-07-26).** Settled 2026-07-23; landed 2026-07-26.
 Reshaped from the old "provenance + null-test verify" M10. Two decisions were fixed

docs/product/removal-and-prune.md

@@ -2,24 +2,26 @@
 
 Framing, rationale, and open forks behind the two missing removal capabilities:
 **sample-remove** (a sample-level index verb) and **prune** (the file-lifecycle
-path CONTEXT.md keeps forward-referencing but never scoped). The tickable spec
-lives in `PLAN.md` (Phase B point B5 for remove; **Phase R** for prune) and the
-authoritative technical detail in `CONTEXT.md` (§Sample removal, §Prune — file
-lifecycle). This doc holds the *why* — the workflow, the guardrails, the
-index-vs-file boundary, and the forks that need a Daniel decision.
+path the spec kept forward-referencing but never scoped). The tickable spec's
+landed history is in `docs/ARCHIVE.md` (Phase B point B5 for remove; **Phase R**
+for prune) and the architecture detail lives in `src/core/model/CLAUDE.md` +
+`src/shell/bank_ops/CLAUDE.md` (§Sample removal) and `src/core/reclaim/CLAUDE.md`
++ `src/shell/persist/CLAUDE.md` (§Prune — file lifecycle). This doc holds the
+*why* — the workflow, the guardrails, the index-vs-file boundary, and the forks
+that need a Daniel decision.
 
 Status: framed by product-designer (2026-07-23); **all five forks settled by Daniel
 (2026-07-24)** — R-A this-bank-primary, R-B batched REAPER undo points
 (Phase-B-wide), R-C trash-preferred-with-unlink-fallback, R-D owned-file manifest
 (seam lands early in Phase B / capture), R-E manual action + panel button. The
-decisions are folded into the fork sections below and into the B5 / Phase R spec
-prose in CONTEXT.md and the tickable points in PLAN.md.
+decisions are folded into the fork sections below and into the B5 / Phase R
+history in `docs/ARCHIVE.md` and the architecture docs above.
 
 ---
 
 ## The one boundary that governs everything: index vs. file
 
-ReaSampler already draws a hard line, stated repeatedly in CONTEXT.md: **a bank
+ReaSampler already draws a hard line: **a bank
 operation touches the *index*, never the *file*.** Move, copy, evacuate, and
 delete-bank are all index-only; files persist on disk "until prune." Every
 removal capability below sits on exactly one side of that line, and keeping the
@@ -120,7 +122,7 @@ line. It is the verb Phase B forgot, not a new pillar.
 
 ---
 
-## Prune — the file-lifecycle path CONTEXT.md kept promising
+## Prune — the file-lifecycle path the spec kept promising
 
 ### What the user is doing
 
@@ -131,7 +133,7 @@ purpose. Over a long project the bank folder accumulates dead `.wav` files that
 cost disk and clutter. **Prune is the reclaim pass**: "sweep the bank folder,
 delete the files nothing references, tell me what you reclaimed."
 
-This is the path CONTEXT.md forward-references in at least four places ("files
+This is the path the spec forward-references in at least four places ("files
 persist on disk until prune," "the capture/prune path reclaims it") but never
 scopes. It is a real, promised capability with **no phase, no module, no point**
 — a dangling reference the plan has to make good on.
@@ -141,8 +143,8 @@ scopes. It is a real, promised capability with **no phase, no module, no point**
 ReaSampler already shipped this exact shape once. Design View's `view_mode_model`
 has **`ViewModeModel::reconcile(liveGuids)`** — a pure function fed the live set
 (the tracks that still exist), returning the residual membership entries to drop
-(CONTEXT.md §Design View: "prunes orphaned snapshots on every toggle/load;
-tolerates unknown/stale GUIDs (prune on reconcile)"). Prune is the **file-pool
+(`src/core/view/CLAUDE.md`: "tolerates unknown/stale GUIDs (pruned on reconcile
+via `ViewModeModel::reconcile(liveGuids)`)"). Prune is the **file-pool
 mirror of that pure pattern**:
 
 > `reconcile(liveGuids)` reconciles *membership entries* against *live tracks*.
@@ -224,7 +226,7 @@ Prune is **not** a Phase B point. Three reasons it earns its own lettered phase
 
 1. **It is a different pillar.** Phase B is the *bank container* pillar
    (index-only, non-destructive, above the file). Prune is the *file lifecycle*
-   pillar (the one path that deletes files). CONTEXT.md already names it as a
+   pillar (the one path that deletes files). The spec already named it as a
    separate concern every time it says "the capture/**prune** path" — file
    lifecycle is spoken of as its own thing, owned by neither the capture nor the
    bank layer. Giving it its own phase matches how the spec already talks about it.
@@ -337,7 +339,8 @@ capture).** The book tracks the set of files it has created; prune reclaims
   ext-state**, and Phase R's R1/R2 *consume* that manifest. The exact persistence
   shape — a sibling ext-state key vs. folded into the `banks` blob — is a small
   residual to settle at build; the **manifest-now decision is firm**. (Settled
-  2026-07-24; the up-front point is added to Phase B / the capture path in PLAN.md.)
+  2026-07-24; the up-front point is recorded in `docs/ARCHIVE.md` under Phase B /
+  the capture path.)
 
 **Fork R-E — prune trigger: manual-only vs. offer-on-orphaning vs. periodic.
 SETTLED: MANUAL ACTION + PANEL BUTTON.** Prune runs via a bindable manual action

docs/product/versioning-and-release.md

@@ -8,8 +8,8 @@ concrete and decidable:
 2. **A beta side-channel** — so development can continue and a beta build run
    *alongside* the stable one without the beta clobbering the release.
 
-This doc holds the *why*, the forks, and a recommendation. When Daniel picks, the
-tickable points land in `PLAN.md` and the deploy/build wiring hands off to dev-ops.
+This doc holds the *why*, the forks, and a recommendation. The tickable points'
+landed history is in `docs/ARCHIVE.md`; the deploy/build wiring hands off to dev-ops.
 This is a framing note; it changes no source or CMake.
 
 Status: framed by product-designer (2026-07-26); **all four forks settled by Daniel
@@ -54,7 +54,7 @@ Two sharp edges follow directly and recur throughout this note:
   Both binaries reading/writing the same namespace on the same open project means a
   **beta can read — and rewrite — a stable project's saved bank/view state.** Given
   the forward-only migrations already in the design (legacy `bank_index` retired
-  after promotion; `banks` authoritative thereafter — CONTEXT.md §Multi-bank), a
+  after promotion; `banks` authoritative thereafter — `docs/ARCHIVE.md` §Phase B), a
   beta that writes a newer schema into a project a user then reopens in stable is a
   real corruption path, not a theoretical one.
 

docs/product/visual-design-language.md

@@ -16,11 +16,12 @@ written after Daniel DAW-tested the S1–S6 instrument:
 revised 2026-07-26 (Daniel)** from the single electric-cyan accent to a **three-accent
 pastel system** (primary/secondary/tertiary = pastel lime green / pastel teal / pastel
 purple) — see §6. (A stylish-font upgrade was considered and **declined** by Daniel — no
-font bundling/redistribution; the kit keeps its current cached-font face.) The build points it feeds live in
-**PLAN.md §Phase L** (**L1** the shared LICE drawing kit, **L2** the dock-panel layout
-redesign, **L3** the VST editor + embed-strip restyle) and **CONTEXT.md §Phase L** (the
-design-system spec). Toolkit facts below are **verified against the vendored `vendor/WDL`
-tree**, not lore.
+font bundling/redistribution; the kit keeps its current cached-font face.) The build points it
+fed have landed; their history is in **`docs/ARCHIVE.md`** ("Phase L — Look-and-feel", **L1** the
+shared LICE drawing kit, **L2** the dock-panel layout redesign, **L3** the VST editor +
+embed-strip restyle) and the architecture now lives in **`src/core/ui/CLAUDE.md`** /
+**`src/shell/panel/CLAUDE.md`** (the design-system implementation). Toolkit facts below are
+**verified against the vendored `vendor/WDL` tree**, not lore.
 
 > **Phase-boundary note (2026-07-26).** This look-and-feel effort was originally drafted
 > as Phase S points **S0-DS** (the shared kit) and **S14** (the panel refresh). It was
@@ -497,7 +498,7 @@ within the pastel intent — is one file.
 
 ---
 
-## 5. The build shape (feeds PLAN.md / CONTEXT.md §Phase L)
+## 5. The build shape (landed history in `docs/ARCHIVE.md` §Phase L)
 
 Three points and their sequencing.
 
@@ -547,7 +548,7 @@ draw it.
   affordances, per-selection **move / copy / remove** sample menu.
 - **Prune** button (R-E) — the byte-deleting action, `warn`-colored.
 
-*M11 adds (dev PLAN.md M11 — merging now):*
+*M11 adds (landed — `docs/ARCHIVE.md` Milestone 11):*
 - **Action trigger buttons** — clickable buttons that fire the capture + provenance
   action family directly (capture item / capture track scopes, re-capture from source,
   resample-and-mute-source, batch capture, conform-on-insert, insert-at-cursor, drag-out,