Repository navigation
fix: complete 1.0 release-boundary audit and acceptance - #340
Merged
Merged
Conversation
This was referenced Nov 1, 2026
logohere
marked this pull request as ready for review
November 1, 2026 09:50
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
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.
Scope
Closes #334 and #335; completes source/package preparation for #336. Stacked on #339. Target: first 1.0.0 release, not an unshipped patch increment.
Evidence
benchmarks/retrieval/release-build-review.jsonanddocs/path-performance.md; no universal speedup claim.docs/v1-security-audit.md.Current-head runtime and pinned Spec Kit matrix checks must finish before merging. Production merge/tag/publication and registry/npm/Bun post-install verification follow the retained-artifact checks; no deployment is inferred from local packing.