Repository navigation
fix: correct hooks reproduction and published release links - #28
Merged
Merged
Conversation
AlexMikhalev
changed the title
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.
The downloaded hooks reproduction could ask the coding host to append a literal period to
python3 validate-brief.py --chek. The command correctly failed the exact permission check, so novalidation.jsonwas produced. Delimit the exact command in a fenced block and explicitly prohibit added arguments or punctuation.Rebuilt only the reproduction script and its ZIP/checksums. The fixture, permission rules, adapter, assertions, recorded outputs and demo video remain unchanged.
Validation: all 32 website tests pass. Two fresh reproductions (four native host sessions) submitted the exact typo, observed baseline exit 2, executed the rewritten
--checkcommand with exit 0, and produced the expectedvalidation.jsonSHA256. A regression check binds the prompt command to the fixture’s exact permission allowlist. Original failed-run evidence is retained locally.The release channel promotion also exposed a stale site version: update
extra.release_versionto the published v1.21.20. All 12 advertised targets resolve against that version; no recorded demo identities are changed.