Add guided CLI reports and recover release verification - #33
Merged
Merged
Conversation
This was referenced Sep 13, 2026
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.
Problem and change
Add a guided terminal flow that scans a URL, file or directory and saves an HTML report. Recover post-publication npm verification with bounded visibility polling against the exact release source; also update supported dependencies, Action pins, skill safety guidance and installation docs.
Includes the changes covered by #21, #23, #25, #26, #27 and #28. Keeps Node 24 types; #24 remains deferred.
Validation and impact
npm run release:checkpassed on Node 22.12.0 and 24.11.1, with 275 tests per runtime and byte-identical tarballs. GitHub CI will validate this PR.For reviewers, check that cancellation cannot leave an output file and release verification retries visibility delays only.