Took a virtual-queue protected action BEFORE admission — skipped the wait, a queue-bypass bot
bh.arena_queue_bypass · convicts
What it catches
Kitsune arena challenge-solve coherence (waiting-room / virtual-queue gate): the queue admits a ticket only after a controlled wait (issuedAt+admitAfter). A client that POSTs the protected action /arena/queue/act on a KNOWN ticket BEFORE that admission instant is deliberately skipping the wait — the fairness mechanism the queue exists to enforce. FP-SAFE BY CONSTRUCTION: a real human's page only enables the action after GET /arena/queue/status reports admitted, so a human client never POSTs /act early; only a script that bypasses the page UI does. The gate fails structurally (ok:false, not-admitted) and the arena emits anomaly:queue_bypass, which the detector's /arena/queue/act relay joins to ks_sid (shared _join_arena_anomaly map) — a passed OR failed gate corroborates the coherence verdict (the arena thesis, honeypot-style: a bot that trips the trap is convicted even though it did not pass). This is the wait-behaviour complement of bh.arena_queue_superhuman: superhuman = acted too fast AFTER admission; bypass = acted BEFORE admission. An unknown/garbage ticket id does NOT fire (only a real, issued ticket acted on early). Convicting (w0.85). GROUNDED LIVE 2026-07-03: a client that POSTs /act immediately after GET /queue (before the 1s wait) trips the anomaly and the joined session convicts; a human waits for admission and never fires it. See docs/research-radar.md (arena waiting-room loop).
Signals it reads
behavioral.arena_queue_bypass
How it fires
present
Bypassed by 10
Frontier evaders that reach the detector uncaught (scored only suspicious, defeating every convicting tell) — this check is not one that stops them. The red-team frontier this detection still has to convict.