Skip to content

docs: point the grounding mode switch at the Render database - #789

Merged
thomasluizon merged 1 commit into
mainfrom
thomasluizon/ticket-21-grounding-readme
Oct 19, 2026
Merged

thomasluizon merged 1 commit into
mainfrom
thomasluizon/ticket-21-grounding-readme

Conversation

@thomasluizon

Copy link
Copy Markdown
Owner

Summary

The grounding README (thomasluizon/orbit-tickets#21, orbit-api#784) told the operator to flip AstraGroundingEnforce in the Supabase SQL Editor. The Supabase project is deleted and the API's data lives on Render PostgreSQL, so the mode switch now points there. Documentation only.

Test evidence

Documentation only; no code or test changes.

Manual steps

None.

🤖 Generated with Claude Code

Production data lives on Render Postgres; the Supabase project is deleted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes
Reviewed the grounding mode-switch documentation against the API's database configuration and flag-loading code.

  • Database target: Replaces the Supabase SQL Editor reference with the API's Render PostgreSQL database, matching the Terraform configuration. The SQL and application behavior are unchanged.

Tests were not run because this change is documentation-only.

Pullfrog  | View workflow run | Using gpt-6.1-sol | 𝕏

@sonarqubecloud

Copy link
Copy Markdown

@thomasluizon
thomasluizon merged commit 3330b8c into main Oct 19, 2026
20 checks passed
@thomasluizon
thomasluizon deleted the thomasluizon/ticket-21-grounding-readme branch October 19, 2026 16:05
thomasluizon added a commit that referenced this pull request Oct 19, 2026
…EADME (#746) (#790)

* Remove social runtime surfaces (ORB-233) (#787)

* Remove social runtime surfaces (ORB-233)

* Finish social signup assertions and reference cleanup

* ci: exclude the retained public profile shape from coverage

The record is never built after the social removal; it stays only so the
profile response schema keeps its shape for old clients until #685, and the
committed OpenAPI snapshot holds that shape.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 7c79309)

* docs: point the grounding mode switch at the Render database (#789)

Production data lives on Render Postgres; the Supabase project is deleted.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 3330b8c)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant