Release archive
3.2.170

CRYPTO-PDF-COVER-PROFILE-CONTEXT (Report Usability)

Release v3.2.170 focuses on CRYPTO-PDF-COVER-PROFILE-CONTEXT (Report Usability).

FixedInternal
CRYPTO-PDF-COVER-PROFILE-CONTEXT (Report Usability)

Release digest

Fixed

  • CRYPTO-PDF-COVER-PROFILE-CONTEXT (Report Usability) — The Intelligence PDF first-page subtitle now includes the descriptive report package profile such as Tokenless Readiness Profile, so readers see the report context before reaching the classic body.

Internal

  • Added focused PDF contract coverage for the first-page report-profile subtitle.
  • Expanded realistic PDF regression fixtures so live-token, tokenless, thin-data, and security-rich reports must preserve their expected descriptive package profile labels.
  • Tightened the regression sample checker with cover-scoped required text so first-page profile labels cannot pass solely because the same label appears later in the classic report body.
  • Extended the downloaded-file PDF contract verifier so Intelligence exports must keep a first-cover Executive readout | ... subtitle with a known report package profile label.
  • Added the detected cover_profile to file/download contract results and post-deploy smoke summaries, making the checked report profile visible in CI artifacts without opening the PDF.
  • Added Intelligence cover-profile labels to regression sample manifests and local QA command output.
  • Updated docs/architecture/CRYPTO_REPORTS.md because this expands the internal executive-readout contract. Public-docs decision: no user-facing docs change required because the profile labels were already documented and rendered in the PDF body; this tightens regression coverage for that existing profile context.

Technical notes