Skip to content

chore: qsl runtime compatibility metadata #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pigbibi merged 2 commits into from
Jul 3, 2026
Merged

chore: qsl runtime compatibility metadata #91

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e99d96
chore: add qsl metadata for runtime platform compat
Pigbibi Jul 3, 2026
9644037
chore: mark qsl transition mode
Pigbibi Jul 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,12 @@ python -m pip install -r requirements.txt
python -m pytest -q
```

## QSL compatibility status

- Added `qsl.toml` with `tier = "runtime-platform"`, `ring = 3`, and `compat.bundle = "2026.07.0"` for runtime compatibility tracking.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add the missing QSL metadata file

This newly added status says qsl.toml was added for runtime compatibility tracking, but the committed tree for beb18efe701928ec3403e3b397215c91ae8b57f1 only changes README.md, and a repo-wide search finds no qsl.toml. Any QSL compatibility tooling or audit that relies on the metadata file will still see this repository as untracked while the README now gives the opposite signal, so the metadata file should be committed or this claim should be removed.

Useful? React with 👍 / 👎.

- Current dependency workflow is still `requirements.txt/requirements-lock.txt` + `pip`; migration to `pyproject.toml + uv.lock` is intentionally deferred due runtime entrypoint/dependency bootstrap compatibility risk.
- TODO: keep this repository under observation and schedule a low-risk migration once runtime bootstrap can retain existing scheduler/entrypoint behavior.

## Useful docs

- [`docs/binance_platform_rename_checklist.md`](docs/binance_platform_rename_checklist.md)
Expand Down
14 changes: 14 additions & 0 deletions qsl.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
[qsl]
repo = "BinancePlatform"
tier = "runtime-platform"
ring = 3
allow_legacy = true
enforce_bundle = false
migration_mode = "pyproject-uv-poc"

[qsl.requires]
quant_platform_kit = "6d3675914eb5d3fe072d3212a90dfb55fe1c1df4"
crypto_strategies = "84e7bf5566167861f7b53bf74261364d055cd30f"

[qsl.compat]
bundle = "2026.07.0"
Loading