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 3ca5b30.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3ca5b307d6

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

Update the metadata test with the bundle bump

With this value changed to 2026.07.1, the existing tests/test_qsl_metadata.py::test_qsl_metadata_has_runtime_platform_fields still asserts that qsl["compat"]["bundle"] == "2026.07.0", so the repository's targeted metadata test now fails on every run (python -m pytest tests/test_qsl_metadata.py -q). Please update the test fixture/expectation together with the QSL bump so CI is not left red.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Keep QSL requires aligned with installed pins

The runtime install path still uses pyproject.toml/uv.lock, and those files continue to pin QPK/US/HK to the previous SHAs (pyproject.toml:24-26, plus the corresponding lock entries), so deployments and CI will execute the old dependency commits while this metadata advertises the new 2026.07.1 bundle requirements. Please update the actual dependency pins and lockfile with these refs, or leave qsl.requires on the versions that are really installed.

Useful? React with 👍 / 👎.