competition-runtime-routing

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