competition-supply-chainlisted

# Competition Supply Chain 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 provenance, dependency drift, build output, release flow, or what runtime artifact actually got shipped. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Split the problem into source, dependency resolution, build, packaging, publish, and runtime consumption. 2. Decide where the first divergence occurs between intended artifact and runtime artifact. 3. Keep provenance as a compact chain, not a scattered set of observations. 4. Reproduce the smallest possible build or package path that still shows the issue. 5. Separate checked-in intent from what the pipeline actually emitted. ## Workflow ### 1. Trace Provenance End-To-End - Map source checkout, lockfiles, dependency fetch, pre/post-install steps, build scripts, packaging, publish target, and runtime consumer. - Compare declared version, resolved version, and shipped artifact. - Note registry, cache, mirror, or CI environment differences. ### 2. Reconcile Build-Time And Runtime - Compare manifests with image layers, mounted secrets, generated files, and runtime hooks. - Identify whether the decisive mutation happens in dependency install, build