AFTER / HEAD — server follow-up dispatch
Commit: 0ec6bba3f34f101726d60c0c7c946393ea32a1de
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                            45.2             32.6–64.6
   2,000                           163.4             97.7–241.3
  15,000                           343.7             122.7–491.9

All measured samples, in sample order (ms):
N=0: 46.6, 45.2, 59.7, 44.4, 64.6, 35.3, 32.6
N=2,000: 112.2, 241.3, 97.7, 238.2, 235.0, 110.9, 163.4
N=15,000: 491.9, 122.7, 370.9, 377.1, 263.1, 238.0, 343.7

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

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.
