competition-container-runtimelisted

# Competition Container 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 challenge is really about what the live container or pod is doing now, not what the checked-in manifest claims it should do. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Split intent from reality: manifest, image, startup, live mount, live route, live process. 2. Map host -> proxy -> container or pod -> mounted volume -> consuming process. 3. Keep secrets, rendered config, init output, and sidecar output separate from static manifests. 4. Prove one minimal live path from mounted or injected state to reachable behavior. 5. Reproduce the effect with the smallest runtime-specific chain. ## Workflow ### 1. Map The Live Runtime - Compare compose or kube manifests against running containers, pods, mounted volumes, env, sidecars, init containers, and entrypoints. - Identify which process actually consumes the mounted secret, rendered config, or shared volume output. ### 2. Trace Route And Mount Boundaries - Map virtual host, reverse proxy, service, container port, filesystem mount, and runtime-generated file paths together. - Record whether the decisive state is image-baked, env-injected, mounted later, or written by