Skip to Content
PredictorSDK

Faster matching lookups and numeric-team spread safety

FixInfra

Sports matching now treats digits embedded in team names as names, not betting lines. A live San Francisco row correctly carried +2.5, but the production contract check read the 49 in “49ers” and incorrectly failed the release; the same permissive pattern also existed as an ingestion fallback. Both paths now share one conservative parser that accepts exactly one standalone number, understands a typographic minus, and refuses dates, scores, records, and other ambiguous labels. Structured provider line metadata takes precedence over text; a malformed structured value is refused rather than replaced from the title. This also protects names such as the Philadelphia 76ers.

Direct matching lookups now use an immutable, run-scoped Valkey index instead of decoding the complete sports snapshot for every requested identifier. The index retains its backward-compatible wire shape while new readers fetch only requested fields from a run-scoped Valkey hash. Versioned metadata verifies the run and hash cardinality; legacy indexes fall back to the previous scan, while partial, malformed, or cross-wired hash data fails closed. Settled-event lookups keep their archive-aware path. API dependency work, including Valkey socket I/O, is bounded inside the server write deadline so a stalled read can return a structured service error instead of closing the connection as an unexplained EOF. Deployment smoke checks also require every affected service rollout and reject stale provider snapshots. No response schema changed.