Cricket Intelligence API starts in deterministic local mode with no external providers, enrichment, models, or ingestion.
The status endpoint exposes the repository snapshot and provider capability flags without leaking a filesystem path.
A real API request answers the LBW question from checked-in repository knowledge.
The selected 2011 World Cup fact is returned from the curated history snapshot.
The India query preserves its team response contract while clearly reporting that archive statistics are unavailable.
The unconfigured live-score boundary returns HTTP 503 with an external-provider label.
The API denies an untrusted origin, rejects an oversized body, adds security headers, and hides the Express signature.
Nineteen routing cases and five real HTTP tests pass; the runtime dependency audit reports zero known vulnerabilities.
Architecture, data provenance debt, optional adapters, and the release non-claims remain explicit.