feat: build a typed Sallyport acceptance fixture - #1
Merged
Conversation
zsumz
marked this pull request as ready for review
August 9, 2026 22:11
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
5f5a83fb553b6e408dff0bd1759ca8abe51e0e6bWhy
The previous repository proved only one older staging checkpoint. It did not
carry Sallyport's current protocol pin, a typed downstream contract, durable
disposition evidence, or the quality gates used across the surrounding zsumz
projects.
Impact
sallytestremains intentionally tiny and should not be used as an applicationdependency. The prepared
0.0.2-fixture.0canary will publish only under thefixturedist-tag after the protected branch, npm 2FA, and Sallyportfinalization gates are satisfied.
Validation
npm ci --ignore-scriptsactionlintnpm run release:checknpm pack --jsonnpm run release:smokezsumz <shawn@zsumz.com>