The compatibility lifecycle is quarantined -> diagnosed -> minimized -> admitted or rejected.
Admission requires:
- explicit permission for diagnosis and minimized regression use;
- a minimized reproducer whose hash differs from the source artifact;
- a passing disclosure scan bound to the reproducer;
- a generic fix identity and deterministic regression test identity;
- recorded deletion of raw customer bytes.
Public redistribution requires separate permission. A clean scan does not grant rights.
buildCompatibilityCaseRecord in @runstamp/contract builds the hash-bound record and rejects incomplete admission. The customer upload and case-management service is not yet generally available. Use the documented support and contracting route before you share a production file.