chore: bump qsl compat bundle to 2026.07.1 (phase-2 runtime)

[Pigbibi]

Summary

• Update qsl.toml: bump qsl.compat.bundle to 2026.07.1.
• Phase-2 runtime compatibility sweep for QSL warning convergence.
• No functional behavior changes intended.

Validation

• Verified via \� minimal repo checks in this branch before PR.
• clean.

Notes

• If any previously failing tests exist, they are pre-existing unless explicitly introduced in commit e26e955.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e26e955b41

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

Keep qsl requires aligned with install pins

The refs declared here no longer match the package commits the runtime actually installs: pyproject.toml:21-23 and uv.lock still pin QuantPlatformKit/UsEquityStrategies/HkEquityStrategies to the old SHAs, while Dockerfile and env-sync install via uv sync --frozen --no-dev. Deployments will therefore keep importing the old dependency commits even though qsl.toml advertises the 2026.07.1 bundle, so update the install pins/lockfile alongside this metadata bump or leave these refs unchanged.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Update the qsl metadata test with the new bundle

With the bundle now set to 2026.07.1, python -m pytest tests/test_qsl_metadata.py -q fails because tests/test_qsl_metadata.py:15 still asserts 2026.07.0. Please update the test expectation or make it derive the accepted bundle from the same source as this metadata change.

Useful? React with 👍 / 👎.