Restore the bank fold and usage publish to the resume path, guard setActive against repeats, and make the meter fold's bound literal

The resume also hands back to a full reload when the fold moves the loaded capture's decode source, so the refs table and the audio cannot skew.

docs/product/instrument-control-surface.md

@@ -1409,6 +1409,15 @@ back through the full reload, which is what keeps the pre-v10 legacy lift reacha
 untouched: dynamic latency ships and the deactivate/reactivate is still the accepted cost —
 it is simply a much cheaper one.
 
+**What "cheaper" does NOT mean: skipping the bank fold.** `reloadInstrument` also runs the
+recapture sync and the `rsusage_` prune-protection publish, and with no editor open the
+activation is the only place either happens (`pollBankSync` runs off the editor's sync tick and
+nothing else). Both are a `GetProjExtState` plus a parse — neither disk nor decode — so both run
+on the resume path too, and a fold that moves the loaded capture's decode source hands back to
+the full reload rather than resuming PCM the bank has superseded. A resume that refreshed the
+refs without re-decoding would be the worst of the three: the table would name a recapture's new
+file while the voices played the old one.
+
 ---
 
 ## 8. Forks — SEVEN ruled (one later reversed), NONE open
@@ -1484,7 +1493,7 @@ than just counting:
 4. **The verification requirements survive unchanged**, because they were always about the
    `kIoChanged` scar (a dual-mono capture panned hard right by a prior mid-session
    `restartComponent`), not about this flag.
-5. **The reduction is filed**, with a trigger condition, in `docs/TODO.md`.
+5. **The reduction was filed with a trigger condition and has since LANDED** (Γ-W3 — §7.11).
 
 ### 8.3 Γ-F7 — RULED: signal flow. The parameter order