Include dynamic volatility context in Telegram logs

[Pigbibi]

Summary

• add SOXL dynamic volatility Telegram translations in zh/en
• include dynamic threshold fields in signal_snapshot logs
• add snapshot coverage for rolling-threshold metadata

Verification

• PYTHONPATH=/home/ubuntu/Projects/QuantPlatformKit/src python -m pytest tests/test_signal_snapshot.py -q
• PYTHONPATH=/home/ubuntu/Projects/QuantPlatformKit/src python - <<'PY' ... direct build_translator smoke test
• python -m py_compile notifications/telegram.py application/signal_snapshot.py tests/test_rebalance_service.py tests/test_signal_snapshot.py

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b79a863596

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

Localize nested threshold detail before formatting

When the strategy emits this new dynamic volatility reason in the same structured signal_display format used by the rest of the Telegram renderer, threshold_detail is another translation key such as blend_gate_volatility_threshold_detail_dynamic: .... _localize_structured_text only recursively localizes reason/reasons, so this template inserts that raw key and arguments into the alert instead of the intended human-readable dynamic/fixed threshold text; the new Telegram context is therefore not actually readable for dynamic volatility signals unless threshold_detail is localized before formatting.

Useful? React with 👍 / 👎.