Gate installed LSP runtime provenance#241
Draft
newtontech wants to merge 5 commits into
Draft
Conversation
…' into agent/issue-230-runtime-openqc # Conflicts: # README.md
…' into agent/issue-230-runtime-openqc
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\n- add a 17-entry release target matrix and installed-runtime provenance ledger\n- report source commit, installed commit, tag/manifest/registry versions, executables, and parity failures\n- make nested issue worktrees discover the canonical OpenQC/LSP fleet roots\n- keep the existing 17/17 family and Bohrium contract green while exposing stale managed runtimes\n\n## Tests\n- make format\n- make lint\n- make typecheck\n- make test\n- make check\n- npm run lsp:check-family -- --strict\n- npm run lsp:check-bohrium -- --strict\n- Jest: 81 suites, 1,568 passed, 2 skipped\n- production audit: 0 vulnerabilities\n\n## Deployment status\nThis PR is stacked on #240 so it can exercise the corrected release gate. The current managed .lsp-latest is intentionally reported as 0/17 matching the release matrix; rebuilding it from approved published artifacts is tracked by the 17 per-repository release issues and must complete before this PR is marked ready.\n\nFixes #230