0.00s Queue ordering - BEFORE 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 1.17s $ t3_thread_send QUEUED mode=queue (through CLI) 2.09s Delivery: queued 2.09s ACTIVE: running | QUEUED: queued 7.58s ACTIVE completed; queue release handler still delayed. 7.58s ACTIVE: completed | QUEUED: queued 7.58s $ t3_thread_send NEWER mode=auto (through CLI) 8.40s Delivery: started 8.40s ACTIVE: completed | QUEUED: queued | NEWER: starting 8.40s ACTIVE: completed | QUEUED: queued | NEWER: starting 8.60s ACTIVE: completed | QUEUED: queued | NEWER: running 12.83s ACTIVE: completed | QUEUED: queued | NEWER: waiting 14.25s ACTIVE: completed | QUEUED: queued | NEWER: completed 27.75s ACTIVE: completed | NEWER: completed | QUEUED: running 30.76s ACTIVE: completed | NEWER: completed | QUEUED: waiting 31.97s ACTIVE: completed | NEWER: completed | QUEUED: completed 31.97s Observed execution order: ACTIVE -> NEWER -> QUEUED 31.97s ACTIVE started 2026-11-15T03:01:01.673Z finished 2026-11-15T03:01:06.584Z 31.97s NEWER started 2026-11-15T03:01:08.689Z finished 2026-11-15T03:01:13.133Z 31.97s QUEUED started 2026-11-15T03:01:27.917Z finished 2026-11-15T03:01:31.028Z 31.97s All observations above read from the real server projection (read-only).