Ψ-W1-T1 second-round remediation: ±1-frame bounds tolerance, self-cleanup a refused render, hedge two unverified render-source inferences

Loosens the exact-bounds gate against REAPER's edge rounding; deletes the bytes a BoundsMismatch refusal writes, per prune_fs's self-cleanup carve-out.

docs/TODO.md

@@ -512,3 +512,31 @@ wrong when they do not.
 **Done looks like.** A `SelectedItems` recapture either reproduces its recorded audio
 from the recipe alone, or refuses with a message naming what the recipe cannot pin
 down.
+
+## An overlapping item on the source track itself is not isolated from a ranged item capture — DECIDED, not deferred
+
+**Context (surfaced by Ψ-W1-T1, capture-range-exactness).** The re-source to the
+selected-tracks render (`&128`) needed transient upstream silencing so an item capture
+did not also print folder children and receives; `render_isolation` (`UpstreamIsolation`)
+covers both. A third widening exists in the same shape: a non-selected item on the
+SAME track that overlaps the requested range is now audible in the render, where the
+pre-fix `&32` selected-items source excluded it by construction (that source only ever
+prints the selected items).
+
+**This is a decision, not a gap.** `src/shell/capture/CLAUDE.md` states the reasoning in
+full and it is not repeated here: `UpstreamIsolation`/`render_selection` silence and
+select TRACKS because the recipe that replays a capture stores tracks and a range, never
+item GUIDs — a mute plan keyed to today's overlapping item could not be recomputed at
+replay time, so muting items would make the capture stop reproducing itself. The named
+candidate (a) in `docs/PLAN.md` §Ψ-W1-T1 carried exactly this semantic edge; it was
+weighed against candidate (b) (an item-bounds render with a derived start time) and (a)
+shipped with the edge accepted rather than closed.
+
+**Priority / risk.** Low in the common case (one item per track over the captured range is
+the normal shape); a project with deliberately overlapping items on one track is the one
+that surfaces it, and the practical mitigation is unchanged from before this track:
+select/move the neighbour, or capture at track scope instead.
+
+**Done looks like.** Nothing to do — recorded so a future reviewer does not read the
+non-isolation as an oversight and re-propose closing it against the recipe's stated
+tracks-and-range-only shape.