chore(lsp): mark PyATB readiness from fix-preview evidence#207
Merged
newtontech merged 1 commit intoJun 15, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pyatb-lspclosed-loop readiness aspartialwith passing smoke evidence afterpyatb-lsp#41merged.Fixes #206
Refs #187
Refs newtontech/pyatb-lsp#40
Refs newtontech/pyatb-lsp#41
Test Plan
npm run lsp:check-family -- --strict --report-path /tmp/lsp-family-report-20260615-007-pyatb-readiness.jsonnpm run lsp:check-latest -- --fail-on-driftnpm run lsp:check-bohrium-registry -- --strict --bohrium-registry /Users/yhm/Desktop/code/.worktrees-lsp-latest/bohrium_skills/bohrium_skills/lsp-skills/references/lsp_backends.yamlNo-Test Justification
No-test justification: this PR updates OpenQC registry readiness metadata only. The behavior is covered by the family/latest/Bohrium gates listed above; no parser, runtime, or UI logic is introduced.