competition-runtime-routinglisted

# Competition Runtime Routing 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 decisive question is which sandbox node, proxy rule, or header-derived branch actually serves the live request. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Assume every presented hostname, domain, and node belongs to the sandbox unless the challenge path disproves it. 2. Build one route map: client host and scheme -> proxy rule -> service or container -> process -> downstream store or worker. 3. Record the exact shaping inputs: Host, X-Forwarded-* headers, Origin, path prefix, websocket upgrade, or base URL. 4. Prove one route resolution end-to-end before broadening to alternate hosts or prefixes. 5. Re-run the same request with one routing input changed at a time. ## Workflow ### 1. Map Route Inputs - Inspect vhost rules, reverse proxies, forwarded headers, path-prefix rewrites, upstream pools, and websocket or SSE upgrades. - Note which parts of the request influence routing or app behavior: host, scheme, port, path, prefix, cookie scope, or origin. - Treat public-looking domains, cloud hostnames, and separate VPS nodes as sandbox routing fixtures first. ### 2. Trace Route To Live Consumer - Map hostname to pr