Archive extraction ambiguity

Use it for every uploaded or third-party release archive before extraction, and again when extraction policy changes. Four independent probes detect traversal and platform aliases, order-sensitive symlink or hardlink write-through, case/Unicode/file-directory collisions, and entry-count/size/ratio expansion hazards; symlink targets are parent-relative while hardlink targets use an explicit coordinate mode that defaults to archive-root-relative. A synthesis step joins them into one severity-prioritized extraction decision. It reads a JSON manifest and never extracts, writes, follows links, or accesses the network. Run with input=path/to/manifest.json, or omit input to use the bundled adversarial demo. Limits: findings depend on the supplied manifest and policy, nested archive contents are not recursively inspected, and filesystem-specific canonicalization is approximated conservatively.