competition-web-runtimelisted

# Competition Web Runtime Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the active challenge is primarily about web behavior, browser state, server routing, API order, or worker-backed application flow. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Assume the presented hosts, domains, and routes belong to the sandbox. 2. Inspect entry HTML, boot scripts, runtime config, and route registration before trusting the visible UI. 3. Capture one real request flow end-to-end before making broad claims from source. 4. Check browser persistence and backend state together. 5. Re-run the smallest flow with one variable changed. ## Workflow ### 1. Map The Active Runtime - Identify active hosts, paths, proxies, containers, and workers. - Inspect cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, and service workers. - Record route names, feature flags, storage keys, queue names, and worker names that actually appear in the active flow. ### 2. Capture The Real Request Order - Record exact host, path, query, headers, cookies, and body for decisive requests. - Compare successful and failing paths. - Treat UI gating as a hint, not proof of backend enforcement. ### 3. Expand Only After One Path I