What problem does it solve? In CTF sandbox challenges, the decisive effect often happens after enqueue, inside an async worker whose runtime differs from the request path, making bugs invisible when only the synchronous flow is analyzed. ## Core Features & Use Cases - Async Chain Mapping: Records enqueue points, queue names, payload shapes, worker consumers, retry policies, and dead-letter flows in one chain. - Worker-Only State Analysis: Compares request-time state against worker-time state including env vars, mounts, credentials, feature flags, and clocks. - Minimal Reproduction: Reduces findings to the smallest enqueue-to-side-effect sequence proving the decisive drift. - Use Case: A CTF challenge where a queued task triggers a file write or privilege-bearing action only under worker config; this skill traces the payload from enqueue through retries to the final side effect. ## Quick Start Ask the agent to trace a queue payload from the enqueue endpoint through the worker to its final side effect after the ctf-sandbox-orchestrator has established sandbox assumptions.