Release archive
3.2.236

CRYPTO-EXPLORER-SOURCE-URL-ALIAS-NORMALIZATION (Report QA)

Release v3.2.236 focuses on CRYPTO-EXPLORER-SOURCE-URL-ALIAS-NORMALIZATION (Report QA).

FixedInternal
CRYPTO-EXPLORER-SOURCE-URL-ALIAS-NORMALIZATION (Report QA)

Release digest

Fixed

  • CRYPTO-EXPLORER-SOURCE-URL-ALIAS-NORMALIZATION (Report QA) — Crypto contract/source normalization now accepts explorer source URL aliases such as explorerUrl, blockExplorerUrl, explorer_url, block_explorer_url, etherscanUrl, blockscoutUrl, scannerUrl, and scanUrl when deployed contract evidence is attached.
  • PDF view-model and AI prompt readiness detectors now use the same explorer URL alias family, so reports do not keep a false Contract/source canonicalization gap when Vartovii data already attached source/explorer evidence under those field names.

Internal

  • Added focused crypto project normalizer, PDF view-model, AI prompt, and regression-pack assertions for explorer source URL aliases without exposing raw explorer URLs or contract addresses in report rows or prompts.
  • Updated docs/architecture/CRYPTO_REPORTS.md and the internal analyzer guidance in scripts/analyze_crypto_report_data_gaps.py. Public docs decision: no public documentation update is required because this is an internal evidence-normalization contract and does not change visible report claims, billing, scoring, audit coverage, legal claims, or investment guidance.

Technical notes