docs: correct live Railway project in deployment architecture

[BigSimmo]

Summary

docs/deployment-architecture.md §1 described production as Railway project clinical-kb, service app, at app-production-68ebf.up.railway.app. Verified against the Railway API — none of that is current. Affected area: docs/deployment-architecture.md only.

Claim in doc	Actual (verified 2026-07-20)
Project clinical-kb	Project Database (5deaad0b), env production (6aa16f7b)
Service app	Service Database (app tier) + worker, both SUCCESS, 1 active deployment each
app-production-68ebf.up.railway.app	Returns 404. Live app serves https://psychiatry.tools
Healthcheck /api/health	Railway probes /api/health/ready

clinical-kb (4361c04f) still exists but has zero active deployments — its last four are all REMOVED, newest 2026-07-14. The doc now records it as superseded so nobody railway links a worktree to it and deploys into a dead project. Retiring it is left as an operator decision, not done here.

Also documents that both services are connected to the BigSimmo/Database GitHub repo and auto-deploy on pushes to main.

Deliberately not changed: the region claims. The only region signal I observed was an x-railway-edge PoP header, which identifies the edge location serving the request, not the container region. Correcting it would have been a guess.

Verification

Verification not run: this worktree has no node_modules, so npm run verify:pr-local could not execute locally. CI is the authority. Confirmed locally and against the live system:

• Prettier — pass, CI's exact invocation (--check --ignore-unknown); the file needed reformatting and was formatted before commit
• Production health — GET https://psychiatry.tools/api/health returned {"status":"ok","demoMode":false,...,"supabaseConfig":"ok","openaiConfig":"ok"}, HTTP 200
• Dead domain — GET https://app-production-68ebf.up.railway.app/api/health returned HTTP 404
• Railway API — environment_status shows Database/worker SUCCESS in project Database; app/worker "No deployment" in clinical-kb
• Docs-only change; no runtime surface

Risk and rollout

• Risk: Low. Documentation only — no code, config, or deployment behaviour changes. The risk it removes is larger than any it adds: the stale record pointed operators at a dead project.
• Rollback: git revert the single commit.
• Provider or production effects: None. Read-only Railway API queries and HTTP health probes only; nothing was deployed, linked, or reconfigured.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated deployment architecture documentation to reflect the current production service, region, health checks, replica configuration, and automatic deployment setup.
  • Documented the active ingestion worker configuration.
  • Clarified that the previous deployment project is retired and no longer active.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 69ede570-116d-47b2-bfb3-4572518d85e8

📥 Commits

Reviewing files that changed from the base of the PR and between 23bd588 and 1b02de5.

📒 Files selected for processing (1)

• docs/deployment-architecture.md

---

📝 Walkthrough

Walkthrough

The deployment architecture documentation now describes the active Database Railway project, its app and ingestion services, deployment configuration, readiness healthcheck, and the retired clinical-kb project.

Changes

Railway deployment documentation

Layer / File(s)	Summary
Update deployment topology docs/deployment-architecture.md	Documents the Database Railway project, Singapore region, psychiatry.tools domain, readiness healthcheck, warm app replica, auto-deploy source, ingestion worker, and retired clinical-kb project.

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

Possibly related PRs

• BigSimmo/Database#511: Updates the same deployment architecture documentation and Railway configuration details.
• BigSimmo/Database#516: Updates Railway production hosting guidance in the same documentation.
• BigSimmo/Database#617: Introduces the Database service and readiness healthcheck referenced by this documentation.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the docs update to the live Railway project and deployment architecture, matching the main change.
Description check	✅ Passed	The description includes summary, verification, and risk/rollback details and is mostly aligned with the template.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/railway-deploy-docs-fix-638ad6

---

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