test: align release signing boundary with exact nanopb bounds - #69
Draft
BitHighlander wants to merge 1 commit into
Draft
test: align release signing boundary with exact nanopb bounds#69BitHighlander wants to merge 1 commit into
BitHighlander wants to merge 1 commit into
Conversation
BitHighlander
changed the base branch from
master
to
rehearsal/7143-715-host-base
September 8, 2026 20:29
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.
Preserve the release host suite at 9c39820 and update the oversized-signature test to require the exact transport decoding failure. Keep the existing late-TxAck assertion so rejection must terminate signing. Companion firmware enforces exact byte capacity and aborts workflows on transport failures. All four signing-boundary tests passed on the Bitcoin-only 7.14.3 rehearsal build. This is internal rehearsal; no Copilot requested.