Observed while releasing #334: Production Ops, Operations Web, Gateway, App View, and Charybdis have Railway source.checkSuites=true, but .github/workflows/ci.yml automatically runs only pull_request and merge_group (plus workflow_dispatch), not push on main. After a green protected PR merge, these deployments remain WAITING for a main commit check suite that never starts automatically.
Evidence: Production merge c53f9e2 from PR #336; Railway deployments eaa16e4c-123c-47c4-8019-d358bfbc1b78 (Ops) and baac9c3c-102b-459f-81c0-328483cbcf72 (Operations Web) waiting. Database Migrator succeeded.
Release workaround: explicitly dispatched existing CI workflow on exact main SHA (run 34166552469), preserving the configured gates. Investigate a consistent lasting trigger/gate configuration without weakening required PR validation. This is pre-existing release infrastructure behavior, outside the chart change.
Observed while releasing #334: Production Ops, Operations Web, Gateway, App View, and Charybdis have Railway source.checkSuites=true, but .github/workflows/ci.yml automatically runs only pull_request and merge_group (plus workflow_dispatch), not push on main. After a green protected PR merge, these deployments remain WAITING for a main commit check suite that never starts automatically.
Evidence: Production merge c53f9e2 from PR #336; Railway deployments eaa16e4c-123c-47c4-8019-d358bfbc1b78 (Ops) and baac9c3c-102b-459f-81c0-328483cbcf72 (Operations Web) waiting. Database Migrator succeeded.
Release workaround: explicitly dispatched existing CI workflow on exact main SHA (run 34166552469), preserving the configured gates. Investigate a consistent lasting trigger/gate configuration without weakening required PR validation. This is pre-existing release infrastructure behavior, outside the chart change.