0.00s Queue ordering - BEFORE-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.62s $ t3_thread_send QUEUED mode=queue (through CLI) 1.20s Delivery: queued 1.21s ACTIVE: running | QUEUED: queued 4.24s ACTIVE completed; queue release handler still delayed. 4.24s ACTIVE: completed | QUEUED: queued 4.24s $ t3_thread_send NEWER mode=auto (through CLI) 4.82s Delivery: started 4.82s ACTIVE: completed | QUEUED: queued | NEWER: running 4.82s ACTIVE: completed | QUEUED: queued | NEWER: running 8.24s ACTIVE: completed | QUEUED: queued | NEWER: waiting 8.44s ACTIVE: completed | QUEUED: queued | NEWER: completed 24.32s ACTIVE: completed | NEWER: completed | QUEUED: running 27.53s ACTIVE: completed | NEWER: completed | QUEUED: waiting 27.73s ACTIVE: completed | NEWER: completed | QUEUED: completed 27.73s Observed execution order: ACTIVE -> NEWER -> QUEUED 27.73s ACTIVE started 2026-11-10T21:28:21.239Z finished 2026-11-10T21:28:24.547Z 27.73s NEWER started 2026-11-10T21:28:25.310Z finished 2026-11-10T21:28:28.580Z 27.73s QUEUED started 2026-11-10T21:28:44.761Z finished 2026-11-10T21:28:47.863Z 27.73s All observations above read from the real server projection (read-only).