chore: finish beta production readiness - #9
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
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.
What changed?
Finishes the automatable
0.4.0-beta.1production-readiness work:betadist-tag selectionThe original workspace's two existing JSON deletions were intentionally excluded.
Local verification
npm cinpm run prepublishOnly(60 files, 247 tests)npm run coverage(all thresholds pass)betagit diff --checkThe local npm advisory endpoint reset its connection; GitHub's production audit, scheduled/full audit policy, and dependency review remain fail-closed remote gates.
Human and policy boundary
This PR does not claim stable production readiness. Independent terminal/usability/accessibility sessions, 48-hour beta observation, license-expression choice, and least-privilege site credentials remain explicit external gates.