chore(railway): expose readiness diagnostics

[Coding-Dev-Tools]

Temporary production diagnostic change:

• use /api/health only long enough to route the vendor process and inspect authenticated readiness
• the start command logs the boolean-only serving dependency map
• a follow-up reviewed revert restores /api/ready before completion

Verification: python -m json.tool railway.json

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aa73170b55

ℹ️ 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]

Restore readiness as the Railway health check

When the customer database or embedder cannot initialize, /api/health still returns 200 unconditionally, while /api/ready returns 503 until both dependencies are usable. Pointing Railway at this liveness endpoint therefore lets a broken deployment be marked healthy and receive traffic, despite the Docker health check and hosted deployment guidance continuing to require /api/ready.

Useful? React with 👍 / 👎.