"Give operations teams a first-class way to verify repository availability at startup and runtime, without writing custom probes for every driver."

The Problem Today
Teams deploying repository-backed services usually need liveness and readiness checks, but today each application must hand-roll its own checks for each driver. This causes duplicated code, inconsistent diagnostics, and delayed detection of connectivity or configuration failures.

What We Are Building

• A AddRepositoryHealthChecks() integration that registers repository probes with ASP.NET Core Health Checks
• Driver-specific readiness checks for EF Core, MongoDB, In-Memory, and DynamicLinq-backed repositories
• Configurable probe behavior (timeouts, failure status, tags, and per-repository opt-in/out)
• Startup validation mode to fail fast when mandatory repositories are unreachable
• Standardized diagnostic payloads exposing driver type, repository type, and failure reason

Benefits

• Faster incident detection for data-access outages and configuration regressions
• Reduced boilerplate in consumer applications
• Consistent health semantics across all supported drivers
• Better Kubernetes/container orchestration behavior through reliable readiness signaling