[Programcode]

The staging project brifeyypjauyusmkptkx was renamed in the Supabase dashboard from debate-trainer-staging to DebateOwl Staging. scripts/staging-sync.mjs compared the display name, so debatelab-staging-sync.timer has refused every run since 2026-10-27 21:04 Budapest time (see #248):

Refused: brifeyypjauyusmkptkx is named "DebateOwl Staging", expected "debate-trainer-staging".

Change

• assertStagingTarget now checks the project by ref only, because the ref never changes. The display-name comparison and STAGING_NAME are gone.
• These safety checks are unchanged: SUPABASE_PROJECT_ID, if set, must equal the staging ref; the staging and production refs must differ; the CLI must be able to see the staging ref. Every CLI call still passes --project-ref brifeyypjauyusmkptkx explicitly, so the script can't target production.
• The tests cover any staging name, the older CLI output that has only id, a production override (refused), and a production project named like staging (refused).
• docs/staging.md and docs/operations.md list the projects by ref, with their current names.

Checks

• npm run verify passed locally, because GitHub Actions is billing-blocked: 96 + 5 unit test files, docs, lint, typecheck, build, the offline service-worker test and 47/47 smoke.
• node scripts/staging-sync.mjs --dry-run on the VPS gets past the target check. It reports "Staging already matches this commit." at a079628 and exits 0. Nothing was changed on staging.

After merge, the timer's clone at ~/ops/debatelab-staging-sync/repo checks out the new main on its next 5-minute tick and runs the fixed script. A successful sync closes #248.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[coderabbitai]

Recent review info

Run configuration

• Source mode: Auto
• Repository: Programcode/DebateLab
• Branch: fix/staging-sync-project-name
• File: .coderabbit.yaml
• Commit: d7864e7
• Layers: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Free
• Run ID: fd591cdf-f458-47e0-9112-8eabc06bd7ed

Commits

Reviewing files that changed from the base of the PR and between a04c156 and d7864e7.

Files selected for processing: 4

• docs/operations.md
• docs/staging.md
• scripts/staging-sync.mjs
• src/test/scripts/staging-sync.test.ts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The staging sync now identifies the staging project by its Supabase ref, not its dashboard display name. The documentation and tests reflect this change and describe the project ID requirements.

Changes: Staging Sync Target

Layer / File(s)	Summary
Ref-based staging target identification scripts/staging-sync.mjs, src/test/scripts/staging-sync.test.ts, docs/staging.md, docs/operations.md	The script finds and returns the staging project by ref without checking its display name. Tests cover different project names, legacy CLI entries, and SUPABASE_PROJECT_ID validation. The docs identify projects by ref and describe the sync requirements.

Estimated code review effort: 2 (Simple) | ~10 minutes

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

_{Comment @coderabbitai help to get the list of available commands.}