[pcvantol]

Terminal product evidence contract

Accept the released EP and Forge product-owned SHA-256 evidence namespaces through a separate closed product-reference validator. Typed evidence must cover exactly the selected components and cannot mix with legacy opaque references. Preserve the existing all-legacy contract and the unchanged managed-runtime, pairing and readiness validators.

Distinguish a failed terminal installer acceptance from successful product steps in both the wizard and its safe customer log. Green progress never authorizes a successful summary. No raw helper/provider diagnostics are exposed.

Qualification

• Exact reviewed diff SHA-256: 6fe1656eec480c770fad4fd943461180f90a3c98d87d266df5b50fd8c862f8bc against main 317486d2adb69ff1742afc4995b89c0fd3fe1dc0.
• 72 targeted native tests PASS, including actual Python NativeProductOperationDispatchReceipt serialization into the Swift decoder for EP, Forge and both, plus malformed/wrong/missing/duplicate/mixed evidence and terminal-failure report tests.
• 22 adjacent Python tests PASS; one unchanged root-only protected progress IO test skipped locally. Full protected root/native coverage gates remain required.
• Independent scoped Quality/Security review PASS after correcting mixed-reference admission.
• Real 0.4.30 GUI evidence: product saga COMPLETE and both services running, but product reference namespaces were deterministically incompatible with the native terminal validator. The exact historical transport failure branch is not persisted, so no cosmetic-only or installed E2E PASS is claimed.

Owner approved protected delivery and one separate signed/notarized 0.4.31 release cycle. This source PR does not sign, publish, replace the VM helper, replay CREATE, stop products, modify journals or consume a new VM test attempt.