[Muawiya-contact]

Why

Supabase may pause a Free staging project after a week of low database activity. A database trigger cannot wake a paused project. The existing staging API already has a public /health route that calls a read-only database RPC, so a small external probe provides useful activity and a failure signal without new SQL or credentials.

Changes

• Run a staging-only, uncached health request three times daily from the default develop branch, with a manual workflow trigger for verification.
• Require HTTP 200 and the exact healthy database response. Fail visibly on DNS, transport, HTTP, or response errors, with a direct resume instruction for connection failures.
• Document how to resume a paused staging project, validate the workflow once, and interpret the limits of Free-plan and GitHub schedules.

Validation

• Verified the hard-coded project reference matches the configured staging ref and differs from production.
• Parsed the workflow YAML and Bash; simulated healthy, unhealthy, HTTP-error, malformed-JSON, and failed-transport responses, and checked the fresh URL and no-cache request header.
• Confirmed the production health route's expected response shape. The staging hostname did not resolve from the working environment, so a live staging success is not yet claimed.
• Documentation paths and git diff --check passed.

Rollout and limit

After merge into develop, resume staging in Supabase if it is paused and manually run Check staging database activity once. Keep #472 open until that live probe succeeds. A few external requests usually help prevent Free-plan inactivity pauses, but Supabase does not guarantee uptime on Free, and GitHub can delay or disable scheduled workflows. No production release, SQL migration, secrets, or Cron changes are included.

Refs #472.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-11-04T17:10:43.830195Z We couldn’t complete this review. Comment @codex review to try again.	0e5bc49	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

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

[Muawiya-contact]

ok