Release archive
3.2.165

CRYPTO-PDF-FALLBACK-REASON-BOUNDARY (Report Resilience)

Release v3.2.165 focuses on CRYPTO-PDF-FALLBACK-REASON-BOUNDARY (Report Resilience).

FixedInternal
CRYPTO-PDF-FALLBACK-REASON-BOUNDARY (Report Resilience)

Release digest

Fixed

  • CRYPTO-PDF-FALLBACK-REASON-BOUNDARY (Report Resilience) — Degraded crypto PDF fallback now exposes only bounded public reason codes and labels in response headers and PDF body text instead of raw import, provider, or service exception details.

Internal

  • Added fallback-route coverage proving internal renderer errors, module names, and local paths do not render in fallback PDFs.
  • Updated docs/architecture/CRYPTO_REPORTS.md because this tightens the internal fallback report contract. Public-docs decision: no user-facing docs change required because the visible fallback boundary remains the same while internal reason details are safer.

Technical notes