competition-container-runtime

1# Competition Container Runtime
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 challenge is really about what the live container or pod is doing now, not what the checked-in manifest claims it should do.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Split intent from reality: manifest, image, startup, live mount, live route, live process.
122. Map host -> proxy -> container or pod -> mounted volume -> consuming process.
133. Keep secrets, rendered config, init output, and sidecar output separate from static manifests.
144. Prove one minimal live path from mounted or injected state to reachable behavior.
155. Reproduce the effect with the smallest runtime-specific chain.
16 
17## Workflow
18 
19### 1. Map The Live Runtime
20 
21- Compare compose or kube manifests against running containers, pods, mounted volumes, env, sidecars, init containers, and entrypoints.
22- Identify which process actually consumes the mounted secret, rendered config, or shared volume output.
23 
24### 2. Trace Route And Mount Boundaries
25 
26- Map virtual host, reverse proxy, service, container port, filesystem mount, and runtime-generated file paths together.
27…