RelayPay v0.8.0 — Operations observability and evidence

RelayPay v0.8.0

RelayPay v0.8.0 adds opt-in operations telemetry and reproducible measured evidence without
changing the frozen merchant API.

Included

• append-only transactional audits with structured, credential-free log emission;
• bounded request metadata and hourly usage rollups that never store headers, cookies, secrets,
  or request bodies;
• OpenTelemetry traces for FastAPI, SQLAlchemy, outbound HTTP, Celery, pollers, mocks, and the
  receiver, exported through an opt-in Collector;
• Prometheus latency, throughput, webhook, mismatch, claim-depth, worker, recovery, and
  circuit-state metrics;
• a version-controlled Grafana dashboard under the Compose observability profile;
• a bounded slow-provider fault and repeatable proofs for shutdown, commit-then-crash, Redis
  loss, retry exhaustion, and queue-notification loss;
• rollback-only EXPLAIN (ANALYZE, BUFFERS) before/after index measurement and bounded HTTP
  load measurement.

Compatibility and safety

/api/v1 remains compatible with the v0.6 baseline. PostgreSQL remains authoritative, Redis
remains acceleration only, and no network I/O occurs inside financial transactions.
Observability is disabled by default and captures low-cardinality operational metadata only.

Synthetic data only. RelayPay is not a payment processor. Never submit real payment,
bank-account, identity, or customer data.

See docs/migrations/v0.8.0.md and docs/operations/observability.md. Measured results are
published from the canonical green CI run; they are observations, not production SLOs. This
release does not deploy or host RelayPay.