Supabase branch health is not proof of preview seed readiness

A newly created Supabase preview branch reporting ACTIVE_HEALTHY does not by itself prove that Auth admin queries and application seed queries are ready. Keep those functional operations in the GitHub Actions preview gate, inspect the exact failing boundary, and allow a bounded retry of an idempotent preview provisioning workflow before changing application code. A retry can distinguish a transient failure, but it does not establish the underlying cause or justify repeated retries, skipped checks, or changes to production. Persistent failures still need database and Auth evidence.

Applies when: provisioning fresh Supabase databases for GitHub pull-request previews. Keywords: Supabase preview branch readiness Auth seed database GitHub Actions retry