test(prs-556): add integration tests and docs for deploy-time posture - #456
Draft
pepe-anchor wants to merge 1 commit into
Draft
test(prs-556): add integration tests and docs for deploy-time posture#456pepe-anchor wants to merge 1 commit into
pepe-anchor wants to merge 1 commit into
Conversation
pepe-anchor
force-pushed
the
prs-556-tests-docs
branch
from
August 27, 2026 10:25
d5cd978 to
8be35ee
Compare
pepe-anchor
force-pushed
the
prs-556-tooling
branch
from
August 27, 2026 10:25
7a24b6a to
9e1c761
Compare
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.
Why am I making this PR?
The deploy-time posture needs end-to-end integration test evidence and the published docs must reflect the new requirement.
What am I changing?
Four new integration tests covering all posture+signature combinations. Fix two vacuous tests that were passing under the wrong posture. Update docs: library getting-started, add-a-chain guide, dApp integration page, and gRPC server page all document the deploy-time posture choice.
One change from the original #444: the
examples/library_integration_test.rscall-site update for
create_registry(&ParserConfig)now lands in the parser_appcommit, which is where that signature changes. #444 left the example uncompilable
across three commits.
What is the Linear ticket?
PRS-556
What are the rollback steps?
Revert the commit.
Is this change backwards compatible?
Yes, tests and docs only.
Does this require cross-team/service coordination?
No.
How do I know it works as designed? Which tests exercise this code?
The four new integration tests. Existing doc build pipeline verifies snippets compile.
Verified at this commit:
cargo clippy --all-targets -- -D warningsclean, and thetree here is byte-identical to the pre-rebuild stack tip.