fix: track upload parity deployment inputs

[BigSimmo]

Summary

• Register scripts/check-upload-limit-parity.mjs as a Railway app watch input and as a container/build CI-scope input.
• Add a load-bearing Railway configuration assertion and CI-scope self-test for that deployment input.
• Archive resolved issues #085, #119, and #125, while preserving the upload-limit implementation already merged by fix: guard upload limits in production builds #1441.
• Correction: this merged PR also archived #105 using withdrawn browser evidence. Follow-up PR docs: reopen issue 105 after withdrawn verification #1483 restores #105 to the open ledger.

RAG impact: no retrieval behaviour change — CI scope, deployment watch configuration, tests, and documentation only.

Verification

• npm run check:ci-scope
  • CI change scope self-test passed.
• npm run check:upload-limit-parity
  • Self-test passed; client and server limits both resolved to 150 MB.
• npm run check:outstanding-issues
• npm run check:branch-review-ledger
• npm run docs:check-links
  • 1,422 repository path references resolved on the refreshed branch.
• npm run docs:check-scripts
  • 405 npm script references resolved on the refreshed branch.
• npm run format
• Earlier branch-wide npm run verify:pr-local
  • Runtime/install parity, formatting, lint, typecheck, 437 test files / 4,586 tests passed (3 skipped), production build, client-bundle secret scan, and 36-case RAG fixture validation.
• Focused tests/railway-config.test.ts
  • Not run locally because the repository coordinator held the Vitest lease in another worktree; hosted CI remained the authority.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Disclosures

• CircleCI had already been removed; no CircleCI provider investigation was performed.
• The unrelated verify:ui PWA failure remains disclosed: installed Chrome reported in-incognito.
• Hosted mergeability behavior was not tested locally.
• No provider-backed clinical, retrieval, Supabase, or deployment workflow was run.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 42 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8127bdfc-67a3-4a19-8dce-5ff6cd03bc01

📥 Commits

Reviewing files that changed from the base of the PR and between 4094463 and b7016f6.

📒 Files selected for processing (5)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md
• railway.app.json
• scripts/ci-change-scope.mjs
• tests/railway-config.test.ts

---

_{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: fa9e050bf0

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

[BigSimmo]

Closing as superseded by #1441, which merged to main as d8b034c8a7aa07081bf3f4f62cbfc0841f7d8c00 while this replacement was open. The merged tree contains the upload-limit parity guard and associated CI/build/docs coverage, so merging this stale replacement would duplicate the implementation and reintroduce ledger conflicts. No branch commits were discarded.

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