Release archive
3.2.85

CRYPTO-PDF-EVIDENCE-REQUIREMENTS-REGISTRY (Shared Required Evidence Contract)

Release v3.2.85 focuses on CRYPTO-PDF-EVIDENCE-REQUIREMENTS-REGISTRY (Shared Required Evidence Contract).

ImprovedInternal
CRYPTO-PDF-EVIDENCE-REQUIREMENTS-REGISTRY (Shared Required Evidence Contract)

Release digest

Improved

  • CRYPTO-PDF-EVIDENCE-REQUIREMENTS-REGISTRY (Shared Required Evidence Contract) — Required evidence coverage rules now live in a lightweight evidence_requirements.py registry beside the crypto report section registry. The PDF still renders the same Required Evidence Coverage section, but its rows now come from an explicit stage-aware contract instead of hardcoded renderer copy.

Internal

  • Added a registry contract test that requires stable requirement IDs, stage scope, explicit pdf_decision, safe missing-evidence copy, and handoff action copy for every required-evidence row.
  • Updated docs/architecture/CRYPTO_REPORTS.md to document the shared evidence requirements registry. No public documentation update is required beyond this changelog entry because the visible PDF behavior and public API surface are unchanged.

Technical notes