System API

Local deployment metadata and readiness

📄️Report core readiness and component health

Compatibility probe using the same bounded database and fixed blob-storage directory checks as /api/v1/health/ready. Optional subsystems and archive integrity are not consulted; failures use the legacy generic unavailable envelope.

📄️Run an explicit expensive archive integrity diagnostic

Operator-only, single-flight diagnostic. It is never a liveness or readiness probe and must not be called automatically. A completed diagnostic returns 200 even when its findings are degraded or unhealthy.

📄️Report process liveness without consulting dependencies

This constant-cost probe does not access the database, filesystem, queues, workers, or clock.

📄️Report bounded required-dependency readiness

Checks only the database connection and fixed blob-storage directory identities. Optional recovery and projection work does not make the whole archive unavailable.

📄️Return this generated native API contract

Unauthenticated deterministic OpenAPI 3.1 document generated from the native server annotations for this running build.

📄️Report application version and build provenance

Unauthenticated constant response exposing the running release version, release date, source commit, native API contract version, and deployment profile; it does not consult component health. Release date and build commit are null when their provenance is unavailable.