docs(staging): de-Fly the staging host guidance

[BigSimmo]

What & why

Fly.io was abandoned for Railway (production runs on Railway). This purges the last Fly-specific guidance from docs/staging-setup.md:

• Replaces the **Fly.io \syd`**host recommendation with a host-agnostic note that names Railway as the production host and keeps Cloud Runaustralia-southeast2` as a Sydney-region alternative.
• Drops the now-false Railway is unsuitable — no Sydney region line (production is on Railway).
• Generalises the operator-only "open the Fly.io/host account" step.

Scope is intentionally limited to docs/staging-setup.md. Not touched:

• .github/workflows/docker-image.yml — a general Docker image-build validator (used regardless of host); only mentions Fly in a comment.
• docs/deployment-architecture.md — has active uncommitted edits in another working branch; left for that work.

The untracked fly.toml + tests/fly-config.test.ts scratch files were removed from the working tree separately (they were never git-tracked, so nothing to PR there).

Verification

• No fly/Fly mentions remain in docs/staging-setup.md.
• prettier --check clean.
• Docs-only change; no code/behaviour touched.

🤖 Generated with Claude Code

[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 ↗︎.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 76424b3b-389c-4f9f-896d-9c21e76b96b4

📥 Commits

Reviewing files that changed from the base of the PR and between 307893e and 4d39fe8.

📒 Files selected for processing (1)

• docs/deployment-architecture.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated staging and production deployment guidance to support any OCI-image hosting provider.
  • Identified Railway as the production hosting option.
  • Added Google Cloud Run in the Sydney region as an alternative.
  • Revised runtime secret setup examples to reflect the updated hosting guidance.

Walkthrough

Updated staging and production deployment documentation to recommend any OCI-image host, identify Railway for production and runtime-secret examples, and retain Google Cloud Run in Sydney as an alternative.

Changes

Hosting Guidance

Layer / File(s)	Summary
Update hosting recommendations docs/staging-setup.md, docs/deployment-architecture.md	Replaces Fly.io-specific guidance with OCI-image-host recommendations, names Railway for production and runtime-secret examples, and retains the Sydney Google Cloud Run alternative.

Estimated code review effort: 1 (Trivial) | ~2 minutes

---

✅ Pre-merge checks override applied

The pre-merge checks have been overridden successfully. You can now proceed with the merge.

Overridden by @BigSimmo via checkbox on 2026-07-12T16:16:08.407Z.

❌ Failed checks (1 error)

Check name	Status	Explanation	Resolution
Verification Claims	❌ Error [IGNORED]	PR description has a vague verification claim: “No fly/Fly mentions remain…” without naming the exact check/command and result.	Rewrite verification bullets to include exact command and outcome, e.g. “Ran rg -n 'Fly|fly' docs/staging-setup.md: no matches” or “Not run: reason”.

✅ Passed checks (10 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the staging host guidance change.
Description check	✅ Passed	The description covers the change, scope, and verification, but its headings do not match the required template exactly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Generated And Sensitive Files	✅ Passed	PR only changes two markdown docs; no secrets, credentials, tokens, private keys, or generated/runtime artifacts were committed.
Risky Git Or Deployment Actions	✅ Passed	No force-push/reset/destructive-clean guidance or unconfirmed prod mutations were added; staging/deploy steps use explicit confirmations.
Supabase Project And Schema Safety	✅ Passed	Only docs host-guidance text changed; Supabase project refs, schema/migration steps, and RLS/policy text were unchanged, with no DB/code files modified.
Runtime And Package Manager Integrity	✅ Passed	package.json, .npmrc, .nvmrc, and Dockerfile still pin Node 24/npm 11 and npm ci; no package-manager switch or force/legacy flags were added.
Api Route Failure Handling	✅ Passed	PASS: PR changes are docs-only (staging/deployment docs); no API routes, server actions, RAG, or provider integrations were modified, so the check is not applicable.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/de-fly-staging-doc

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/de-fly-staging-doc

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 307893e6bd

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/staging-setup.md`:
- Around line 54-56: Synchronize the hosting recommendations in staging-setup.md
and deployment-architecture.md by selecting one authoritative production host.
Update both runbooks to name that host consistently, remove contradictory
suitability guidance, and preserve the existing regional alternative and
operator-step context where applicable.

🪄 Autofix (Beta)

✅ Autofix completed

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 87e96e8a-8568-4858-8e91-5462a3ba4903

📥 Commits

Reviewing files that changed from the base of the PR and between 9da527c and 307893e.

📒 Files selected for processing (1)

• docs/staging-setup.md

[coderabbitai]

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Fixes Applied Successfully

Fixed 1 file(s) based on 1 unresolved review comment.

Files modified:

• docs/deployment-architecture.md

Commit: df72ab7d21dd4e3b3f88501619ec4d8ccbd67c30

The changes have been pushed to the claude/de-fly-staging-doc branch.

Time taken: 3m 24s

Ok

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4d39fe85f1

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".