chore: qsl runtime compatibility metadata#81
Conversation
🤖 Codex PR ReviewPlease ensure a human reviewer checks this PR before merging. |
Co-Authored-By: Codex <noreply@openai.com>
9107d51 to
740f24e
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9107d51daf
ℹ️ 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".
|
|
||
| ## QSL Compatibility Metadata | ||
|
|
||
| - Added `qsl.toml` to participate in the runtime compatibility matrix with `tier = "runtime-ops"`, `ring = 4`, and `compat.bundle = "2026.07.0"`. |
There was a problem hiding this comment.
Add the missing qsl.toml metadata file
This line documents that qsl.toml was added and that the repo now participates in the compatibility matrix, but the commit tree contains no qsl.toml or other qsl file (git ls-tree -r 85553f38... | rg '(^|/)qsl\.toml$|qsl' returned no matches). In contexts where the compatibility matrix discovers repos by reading qsl.toml, this change leaves the repo unregistered while the README says the metadata exists; either add the metadata file or remove this claim.
Useful? React with 👍 / 👎.
Co-Authored-By: Codex <noreply@openai.com>
Summary\n- Add qsl.toml metadata for compatibility runtime upgrade mode.\n- Add minimal metadata tests for runtime repos where applicable.\n- For Binance: keep requirements/pip stack and add migration TODO note.\n- For IBKRGatewayManager/SchwabTokenAutoRefresher: metadata-only for non-Python package tooling.