Show TQQQ delever allocation in notifications

[Pigbibi]

Summary

• include TQQQ retained / QQQM redirected ratios in volatility-delever notifications
• pass the new allocation fields through execution metadata and signal snapshots
• pin UsEquityStrategies to fdd39ef0313181bee9083319b87b7175c32b364d

Validation

• python -m py_compile notifications/telegram.py decision_mapper.py application/signal_snapshot.py
• PYTHONPATH=/home/ubuntu/Projects/QuantPlatformKit/src:/home/ubuntu/Projects/UsEquityStrategies/src:. python -m pytest tests/test_notifications_telegram.py -q
• direct zh/en TQQQ risk-control render check passed

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 19944dcd95

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

Omit allocation detail when ratios are unavailable

When dual_drive_volatility_delever_applied is true but the execution payload lacks the new *_retained_ratio/*_redirected_ratio fields and the older *_retention_ratio fallback, this unconditional call still appends an allocation detail rendered as TQQQ retained n/a, QQQM n/a. That payload shape is still supported elsewhere in this repo (for example the TQQQ mapper/snapshot tests only carry the pre-existing delever fields), so older reports or any strategy path that does not populate the new ratios now produce a misleading notification instead of the previous clean risk-control line; consider only adding allocation_detail once at least one ratio can be derived.

Useful? React with 👍 / 👎.