Remove TACO from crisis plugin#60
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c5d2ae011d
ℹ️ 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".
| "strategy_plugin_route_no_action": "未触发危机", | ||
| "strategy_plugin_route_true_crisis": "真危机", | ||
| "strategy_plugin_route_taco_fake_crisis": "TACO 假危机", | ||
| "strategy_plugin_route_unknown_route": "未知状态", | ||
| "strategy_plugin_action_no_action": "不操作", | ||
| "strategy_plugin_action_watch_only": "仅通知", |
There was a problem hiding this comment.
Removing the strategy_plugin_route_taco_fake_crisis / strategy_plugin_action_small_taco entries causes legacy plugin payloads to render raw identifiers in Telegram notifications (taco_fake_crisis, small_taco) because translate_strategy_plugin_value falls back to the original value when a translation key is missing (application/runtime_strategy_adapters.py:50-54). This is user-visible whenever older crisis_response_shadow signal files are still mounted, so notifications can still expose TACO wording in a less readable form instead of a generic status/action.
Useful? React with 👍 / 👎.
1 participant
Remove legacy TACO route/action handling from the crisis plugin translation path. User-facing notifications now use only generic crisis status wording.