0.00s Queue ordering - AFTER 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.94s $ t3_thread_send QUEUED mode=queue (through CLI) 1.89s Delivery: queued 1.89s ACTIVE: running | QUEUED: queued 5.04s ACTIVE completed; queue release handler still delayed. 5.04s ACTIVE: completed | QUEUED: queued 5.04s $ t3_thread_send NEWER mode=auto (through CLI) 5.91s Delivery: queued 5.91s ACTIVE: completed | QUEUED: running | NEWER: queued 5.91s ACTIVE: completed | QUEUED: running | NEWER: queued 9.14s ACTIVE: completed | QUEUED: waiting | NEWER: queued 9.55s ACTIVE: completed | QUEUED: completed | NEWER: queued 25.05s ACTIVE: completed | QUEUED: completed | NEWER: starting 25.25s ACTIVE: completed | QUEUED: completed | NEWER: running 28.27s ACTIVE: completed | QUEUED: completed | NEWER: waiting 28.47s ACTIVE: completed | QUEUED: completed | NEWER: completed 28.47s Observed execution order: ACTIVE -> QUEUED -> NEWER 28.47s ACTIVE started 2026-11-15T03:01:13.073Z finished 2026-11-15T03:01:16.557Z 28.47s QUEUED started 2026-11-15T03:01:17.833Z finished 2026-11-15T03:01:20.977Z 28.47s NEWER started 2026-11-15T03:01:37.038Z finished 2026-11-15T03:01:40.137Z 28.47s All observations above read from the real server projection (read-only).