docs: close Γ-F6 and resequence Phase Γ into three waves

Dynamic latency ships as ruled; the restart cost is re-attributed to our own
setActive and filed in TODO. The reflow splits canvas (W1-T4) from arrangement
(W3-T1); preserve-time-stretch moves to W1-T5.

docs/product/parameter-automation.md

@@ -197,11 +197,18 @@ Two corollaries the parameter work must carry rather than rediscover:
   flag must survive that cycle.
 
 Full reasoning, the SDK quotes, and the required verification steps are in
-`docs/product/instrument-control-surface.md` §3.1.1. **One fork remains open there
-(Γ-F6)** — whether the deactivate/reactivate cost is acceptable in REAPER, with constant
-reported latency as the pre-agreed fallback. If that fallback is taken, the limiter enable
-becomes automatable again and this section shrinks to a footnote; check which way it went
-before writing the parameter list.
+`docs/product/instrument-control-surface.md` §3.1.1. **Fork Γ-F6 is now RULED (Daniel,
+2026-08-01): dynamic latency ships as specced and the deactivate/reactivate is accepted.**
+There is no constant-reported-latency fallback — that option is closed, not shelved — so
+**this section does not shrink to a footnote and the limiter enable does not become
+automatable.** Plan against the not-automatable classification; it is settled.
+
+**One future condition could reopen it, and it is worth knowing about.** The restart is only
+expensive because *this plugin's* `setActive(true)` re-decodes the WAV — not because the SDK
+requires it. `docs/TODO.md` ("Decouple the instrument reload from VST3 activation") files that
+reduction, and **"the limiter enable is wanted automatable" is one of its named trigger
+conditions.** If the parameter work genuinely needs that lane, the answer is to do the
+decoupling first, not to re-litigate the classification.
 
 ---