competition-bundle-sourcemap-recoverylisted

# Competition Bundle Sourcemap Recovery 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 runtime truth lives in built assets, source maps, chunk tables, or obfuscated loader flow rather than in checked-in source alone. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Start from the served artifact set: entry HTML, build manifest, bootstrap bundle, chunk map, and source maps. 2. Record chunk ids, route chunks, loader functions, endpoint strings, and config keys before broad manual deobfuscation. 3. Reconstruct the smallest runtime graph that explains which asset executes now. 4. Keep served artifact truth separate from repository source unless parity is proven. 5. Reproduce the smallest asset-to-runtime boundary that proves the decisive behavior. ## Workflow ### 1. Map The Served Artifact Set - Record entry HTML, script tags, preload hints, manifest files, asset map, chunk registry, and source map URLs. - Note framework-specific artifacts such as route manifests, client reference manifests, or lazy-loader tables when present. - Keep emitted filenames, hash suffixes, and route ownership tied together. ### 2. Reconstruct Runtime Structure - Follow bootstrap code, chunk loaders, module registry, string