Rates Engine v0.5.0-rc.77

[v0.5.0-rc.77] — 2026-05-24

Fixed

• Per-source density genesis ledgers now exact, not rounded
  approximations. sourceGenesisLedger per-source values were
  rounded (e.g., 50,500,000) — under the granular-coverage
  mission, both directions of inexactness are correctness bugs:
  rounding LOW reports false-negative density holes for ranges
  where no contract existed; rounding HIGH silently excludes
  legitimate early ledgers, inflating density score. Replaced
  with exact first-WASM-deploy ledger from each source's
  docs/operations/wasm-audits/<source>.md audit log. Sources
  without an audit yet (cctp, rozo) keep their TODO until the
  walk lands. A new TestSourceGenesisLedgerExact regression
  test in internal/api/v1/diagnostics_ingestion_density_test.go
  pins every audited source to its exact audit-evidence value
  and asserts the Soroban-activation floor (L50,457,424) — any
  drop below it signals "someone re-rounded back to a deploy-era
  constant". (Spans this fix + the prior 92d713a / 0966d6f /
  495b79f follow-ups; final correctness guard for #10.)
• SDK checksum-validation WARN flood actually silenced (#62a).
  The rc.72 env-var fix (QuietS3ChecksumWarnings) was a no-op:
  go-stellar-sdk/support/datastore/s3.go:161 hardcodes
  ChecksumMode: types.ChecksumModeEnabled per request, overriding
  the env-var default. verify-archive's 12-way parallel walk
  flooded journald with ~22k WARN/30s during r1 bootstrap. The
  real fix wraps fd-2 with a filtering pipe at process start +
  drops lines containing "Response has no supported checksum"
  before they reach journald. Fail-soft: if pipe/dup3 errors,
  startup continues with raw stderr. Renamed +
  pipeline.SilenceSDKChecksumWarnings (was
  QuietS3ChecksumWarnings). The env-var approach + its
  upstream-respect rationale is documented in the function's
  doc comment.