diff --git a/docs/plans/2026-11-09-out-of-process-script-runner-design.md b/docs/plans/2026-11-09-out-of-process-script-runner-design.md
index 925035160..8d408907b 100644
--- a/docs/plans/2026-11-09-out-of-process-script-runner-design.md
+++ b/docs/plans/2026-11-09-out-of-process-script-runner-design.md
@@ -709,7 +709,9 @@ per-shard state, restarts in the last hour and the quarantine list. Quarantines
      example 1 week on QA), not a mode to run in production.
    - Exit criterion: zero unexplained mismatches. This is where [A-7] / [A-8] get answered.
    - **Landed in lmxopcua#780 (P2 slice, record in §12.4):** `ShadowScriptRunner`, all three seams, bounded and
-     drop-counted, readiness untouched; docker-dev drill with alarms. The QA shadow week is still to run.
+     drop-counted, readiness untouched; docker-dev drill with alarms.
+   - **Owner decision 2026-11-12: no QA shadow week.** P2 ends with the docker-dev drill; `Shadow` stays available
+     as an opt-in diagnostic but is not a rollout gate. QA goes straight to P3.
 4. **P3, flip on QA, then the other tiers.**
    - Set `Scripting:Runner=OutOfProcess` per node, seam subset first (Calculation, then VT, then alarms; alarms
      last because of the 250 ms budget).
@@ -1643,7 +1645,7 @@ measures the §8 table: p50/p99 added latency, throughput at K=1/2/4, host CPU,
 **Live gates:**
 - docker-dev rig: a deploy with VTs, Calc tags and scripted alarms; drill a runaway script through the
   AdminUI and watch `/uns` go Bad, the quarantine appear, and siblings stay Good;
-- QA shadow week (P2);
+- ~~QA shadow week (P2)~~ — dropped by the owner 2026-11-12;
 - a QA flip with the same drill.
 
 ---