[codex] Route runtime errors to main bot

[Pigbibi]

Summary

• send runtime failure notifications only to the platform main Telegram bot
• rename strategy plugin alert runtime settings to STRATEGY_PLUGIN_ALERT
• sync Cloud Run env workflow to publish new names and remove old CRISIS_ALERT plugin envs
• pin quant-platform-kit to 3b6a0a9bedde72773e188041e0dc48516b38aadc

Validation

• env PYTHONPATH=.:../QuantPlatformKit/src:../UsEquityStrategies/src /tmp/codex-alert-test-venv/bin/python -m pytest -q tests/test_request_handling.py tests/test_runtime_config_support.py tests/test_sync_cloud_run_env_workflow.py
• env PYTHONPATH=.:../QuantPlatformKit/src:../UsEquityStrategies/src /tmp/codex-alert-test-venv/bin/python -m pytest -q tests/test_rebalance_service.py

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c11685f36

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

Preserve old alert vars during the rename

When this workflow first runs after the rename, installations that still have the existing CRISIS_ALERT_* GitHub variables/secrets but have not manually created the new STRATEGY_PLUGIN_ALERT_* names will resolve these new env entries as empty; the sync step then removes the old CRISIS_ALERT_* Cloud Run keys, and runtime_config_support.py only reads the new names, so strategy plugin alert recipients/tokens are silently cleared. Please either fall back to the old variable names while syncing/loading settings or add a migration path before removing the old Cloud Run envs.

Useful? React with 👍 / 👎.