Release archive
3.2.149

CRYPTO-PDF-FALLBACK-EVIDENCE-BOUNDARY (Resilience Contract)

Release v3.2.149 focuses on CRYPTO-PDF-FALLBACK-EVIDENCE-BOUNDARY (Resilience Contract).

FixedInternal
CRYPTO-PDF-FALLBACK-EVIDENCE-BOUNDARY (Resilience Contract)

Release digest

Fixed

  • CRYPTO-PDF-FALLBACK-EVIDENCE-BOUNDARY (Resilience Contract) — Crypto PDF fallback exports now include an explicit Fallback Evidence Boundary with template mode, lifecycle stage, coverage state, security provenance state, advanced-section attachment status, and safe missing-evidence language. Fallback responses now also expose the report contract and PDF schema headers used by full exports.

Internal

  • Added fallback route coverage for contract headers, printable-template fallback copy, missing security/audit provenance language, missing-value guards, and old fallback phrasing that should not return.
  • Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md because fallback PDF output and response headers are user-visible. Public-docs decision: documented as a resilience/readability improvement without safety, audit, legal, trading, or investment claims.

Technical notes