fix: treat Supabase project warning as ready in setup-status - #287
Merged
Conversation
This pull request has been ignored for the connected project Preview Branches by Supabase. |
BigSimmoforce-pushed
the
cursor/production-search-unblock-c40b
branch
from
July 5, 2026 16:44
189009b to
f56c799CompareBigSimmo
marked this pull request as ready for review
July 5, 2026 17:04
Contributor
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. |
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jul 5, 2026
cursorBot
pushed a commit
that referenced
this pull request
Aug 8, 2026
…1761) * issues: capture the in-page nav series (#286 PR 2, #287 PR 3, #288 DocumentViewer decision) and correct #256#256's forms half is disproven against origin/main e71b23b: all six formSections targetIds now render as element ids. Its differential-presentations half is still live, and two DSM routes have the same defect and were never recorded. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GyM49edHSNfm42u1SFDfG3 * issues: correct #256–#288 after review (presentations + DocumentViewer) Presentations shell ownership is already local; DocumentViewer non-adoption is already in search-chrome-behaviour.md. Add #286–#288 to the recommended execution queue and narrow the remaining owner decisions. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
BigSimmo pushed a commit
that referenced
this pull request
Aug 12, 2026
…system rows Archived as verified-delivered or duplicate: #303, #284 (dup of #296), #149, #159, #286, #287, #288, #256, #261, #291. Re-scoped with re-measured evidence: #210 (gate was never missing; the defect is the .next/dev types include), #262 (aliases 228 -> 193), #266 (counts moved, 23 unadopted holds), #275 (premise 'only one implementation' is false — the values leaked to five files). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017paT42ZVMf8jaLtkjFxdy5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Supersedes the earlier broad diff now that #274 (public access rollout) is on
main.Production still reports project check
needs_setupwhenSUPABASE_PROJECT_NAMEis unset, even though the Supabase URL ref is correct (warningstatus). That blockshasReadyPublicSearchSetup()paths in the UI setup panel.Change (minimal)
/api/setup-status: map Supabase projectwarning→ setup checkready(same as correct-ref, missing metadata labels).ready.Dashboard production search resilience and rate-limit fallback are already on
mainvia #274.Verification
npm run typecheck— passtests/setup-status-route.test.ts— 2 tests passPost-deploy
https://psychiatry.tools/api/setup-status→ project check should becomeready