What happens after a suspicious session is diverted? It needs somewhere consistent to keep working.
DungeonQ's new reproducible walkthrough follows that path: write a world record through MCP, read it through HTTP, use a world-only Wrong Ticket, then restart the services and check that the state survives. A separately scoped operator grant permits a bounded follow-up record; independent evidence checks what happened.
You can run the walkthrough locally without connecting a model or production system. From the public repository, with Node.js 24.15.0+:
DungeonQ diverts designated suspicious sessions into persistent synthetic worlds. Human and AI clients use world-only tickets; operators observe and approve bounded adaptation. Inspect recorded runtime checks and the original Astra experiment.
