BEFORE / BASE — server follow-up dispatch
Commit: fc6c68b773db0a3cc7292a703d337a44919164b5
Linux x86_64 | AMD Ryzen 9 9950X (8 vCPU) | Node v26.13.1
7 fresh on-disk databases per size; same machine, alternating commit order.
One untimed warmup per server. HTTP route times orchestrator.dispatch only.
Provider effects parked; SQL capture enabled identically on both commits.

Earlier parent runs     Median ms       Min–max ms
       0                            30.5             22.4–64.2
   2,000                           255.5             129.3–302.7
  15,000                           981.7             780.9–1253.4

All measured samples, in sample order (ms):
N=0: 25.3, 30.5, 28.8, 64.2, 63.0, 33.4, 22.4
N=2,000: 298.7, 255.5, 196.1, 302.7, 271.0, 140.1, 129.3
N=15,000: 1253.4, 1094.6, 981.7, 1008.3, 913.1, 780.9, 889.6

Parent payload SELECT rows (runs / attempts / provider turns):
N=0: 2 / 2 / 1
N=2,000: 2001–2002 / 2001–2002 / 2001
N=15,000: 15002 / 15002 / 15001

PASS 21/21: original task completed, follow-up created,
owner run preserved, and provider-turn binding preserved.
SQL row counts re-run after timing; ordinal-only SELECTs excluded.
