A staging support-queue investigation must verify an environment-specific database connector…

A staging support-queue investigation must verify an environment-specific database connector before interpreting priorities or assignee capacity. If the confirmed staging target is unavailable, do not fall back to production or an unrelated non-production project: report code-derived behavior separately from unverified current staging state. This applies to any live operational review where shared schemas make a wrong-target result look plausible.

Evidence/example (2026-09-19): repository staging configuration identified a distinct protected staging Supabase target, while the callable connectors did not include it; bounded schema probes of the other exposed non-production projects found no Shield issues table or support-priority enums. No live staging P0–P3 counts or assignee state were claimed.