fix: treat Supabase project warning as ready in setup-status

[BigSimmo]

Summary

Supersedes the earlier broad diff now that #274 (public access rollout) is on main.

Production still reports project check needs_setup when SUPABASE_PROJECT_NAME is unset, even though the Supabase URL ref is correct (warning status). That blocks hasReadyPublicSearchSetup() paths in the UI setup panel.

Change (minimal)

• /api/setup-status: map Supabase project warning → setup check ready (same as correct-ref, missing metadata labels).
• Test: warning status returns project check ready.

Dashboard production search resilience and rate-limit fallback are already on main via #274.

Verification

• npm run typecheck — pass
• tests/setup-status-route.test.ts — 2 tests pass
• Prettier — pass on changed files

Post-deploy

• https://psychiatry.tools/api/setup-status → project check should become ready
• Confirm mobile search still works after full feat: complete public access rollout with migrations and public corpus promotion #274 + this deploy

  

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.