0.00s Queue ordering - AFTER-FINAL 0.00s Environment: Linux; real development server + CLI / MCP; replay provider 0.00s Synthetic thread; identical driver; terminal capture 1200 x 720; dark theme 0.00s Timing control: run-end handler delayed 20s; replay prompts wait 3s, both sides 0.00s $ thread start ACTIVE 0.75s $ t3_thread_send QUEUED mode=queue (through CLI) 1.33s Delivery: queued 1.33s ACTIVE: running | QUEUED: queued 4.46s ACTIVE completed; queue release handler still delayed. 4.46s ACTIVE: completed | QUEUED: queued 4.46s $ t3_thread_send NEWER mode=auto (through CLI) 5.02s Delivery: queued 5.02s ACTIVE: completed | QUEUED: running | NEWER: queued 5.02s ACTIVE: completed | QUEUED: running | NEWER: queued 8.24s ACTIVE: completed | QUEUED: waiting | NEWER: queued 8.44s ACTIVE: completed | QUEUED: completed | NEWER: queued 24.52s ACTIVE: completed | QUEUED: completed | NEWER: running 27.54s ACTIVE: completed | QUEUED: completed | NEWER: waiting 27.74s ACTIVE: completed | QUEUED: completed | NEWER: completed 27.74s Observed execution order: ACTIVE -> QUEUED -> NEWER 27.74s ACTIVE started 2026-11-10T21:28:14.295Z finished 2026-11-10T21:28:17.652Z 27.74s QUEUED started 2026-11-10T21:28:18.457Z finished 2026-11-10T21:28:21.568Z 27.74s NEWER started 2026-11-10T21:28:37.858Z finished 2026-11-10T21:28:40.964Z 27.74s All observations above read from the real server projection (read-only).