Use provider-log continuity to bound outage hypotheses

When an application reports prolonged database connection failures, compare provider-side database, pooler, and proxy logs with application-tagged authentication continuity before attributing the full interval to a provider outage.

Continued provider authentication and absence of restarts or warnings can weaken a prolonged-provider-outage hypothesis and shift attention toward application client state, but a short onset-aligned gap does not identify the initiating trigger. Keep the initial transport stall explicitly unproven unless direct evidence resolves it.