ops: reconcile hosted configuration presence

[BigSimmo]

Summary

• harden check:env-parity so GitHub reads are pinned to BigSimmo/Database and Railway reads are pinned to the live production project/environment plus explicit Database and worker services
• cover multiline Zod declarations, .env.example, GitHub variables, per-service runtime requirements, the OpenAI safety-identifier secret, and 30-second provider timeouts
• let check:local-presence safely target an explicit checkout, fill the three approved gitignored local HMAC/probe gaps, and closeEnhance clinical safety and governance #54 with current provider evidence

Production/config evidence

• names-only GitHub secrets/variables parity: PASS; PROD_HEALTH_URL present
• names-only Railway app/worker parity: PASS for project 5deaad0b-675a-4c13-978e-5ca2b5b877f9, production environment 6aa16f7b-d3e8-4aa2-9854-ee9ead9fcbd4
• Ops Digest workflow: active; latest scheduled run succeeded
• Railway app and worker: latest main deployments succeeded
• Supabase Clinical KB Database: read-only names/status proof found the expected retention/auto-toggle schedules and cron_ingestion_jwt / indexing_v3_agent_secret; webhook activation remains separately tracked as Fix Next.js binding to allow Railway healthchecks #25
• primary local checkout: project identity ready; three generated local-only secrets present; no values printed or committed

Verification

• focused parity/local-presence tests: 22/22 PASS
• npm run verify:cheap: PASS; 25 gates, 393 test files, 3,523 passed / 2 skipped
• npm run verify:pr-local: PASS; full unit matrix plus 36 offline RAG fixtures; build correctly skipped as unaffected
• production readiness with the primary env loaded: READY; 8 PASS, 2 non-blocking fresh-worktree env-file-location warnings
• exact-head npm run check:env-parity -- --gh --railway: PASS
• branch-review-ledger guard: PASS, 1,039 records

Risk and rollback

• no application runtime, schema, migration, retrieval, ranking, or UI behavior changes
• Railway JSON necessarily contains values internally; the checker captures it in memory, immediately reduces to names, and never emits or persists values
• value equality across write-only GitHub secrets is deliberately not claimed; no continuity-sensitive secret was rotated merely for comparison
• rollback is a normal revert of the two PR commits; generated local-only values should remain local and are not part of Git rollback

Checks not run

• production build and browser matrix: not selected by the risk-scoped PR-local plan because no build-affecting or UI files changed
• live OpenAI/RAG evaluation: not run; no retrieval or answer behavior changed and no spend was justified

RAG impact: no retrieval behaviour change — configuration tooling, local secret presence, and operator evidence only.

[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]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in:30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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 Plus

Run ID: 6e340a73-ef6c-4460-849c-9e0a3e0d66c5

📥 Commits

Reviewing files that changed from the base of the PR and between a3420d0 and 2d698f8.

📒 Files selected for processing (7)

• docs/branch-review-ledger.md
• docs/operator-backlog.md
• docs/outstanding-issues.md
• scripts/check-env-parity.mjs
• scripts/check-local-presence.mjs
• tests/local-presence.test.ts
• tests/repo-hygiene.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/config-reconciliation-current-20260727

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:8d81e3176e

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

[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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.