Repository navigation
fix(report): verify published cli paths and publication text - #31
Merged
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.
Change
Published-release integration now runs the analyze, saved-Form, comparison and Policy business paths with fixtures from the exact release tag, instead of stopping at installation. Reports inspect encoded credentials before any write, preserving consumer path policy. CLI version examples use an explicit published-version placeholder independent of Action v1.
Accepted scope: SPEC-006 verified installation, faithful reporting and privacy; repository qualification workflow.
Validation
bun run verifypassed: static checks, unit tests, workflow analysis, secret scans and committed bundle reproduction. Synthetic encoded credential and path-policy tests passed. Published-release integration and a real PR comment remain post-publication checks; no draft is accepted by the installer.