Require test-first, fail-closed hardening of frozen inputs

When modifying or auditing governance adjudication, preserve strict provenance and input-safety guarantees. Add deterministic adversarial regressions before changing production code, covering exact frozen pins, byte and canonical hashes, duplicate or malformed JSON, archive member uniqueness and resource limits, regular-file checks, path aliases, and verification/validation races. Every malformed, substituted, or ambiguous input must fail closed without overwriting frozen inputs, and published summaries must report a closed canonicalization gate. After fixes, run focused tests and the full suite, then obtain fresh correctness and security reviews against the exact final tree. Avoid polling, duplicating, or overlapping active work.