Add server-initiated-request-format scenario (#59)#67
Closed
balloob wants to merge 1 commit into
Closed
Conversation
Adds the mid-stream codec renegotiation scenario from #59. Per the audit, no SDK in the matrix emits `stream/request-format` today — every audited SDK defines the struct and parses a server response, but none actually sends it. The scenario is here as the conformance driver for closing that gap; the `stream-request-format-emit` capability is declared only on the aiosendspin server, so every client case fails fast.
This was referenced May 27, 2026
Collaborator
Author
|
Closing per discussion in #68 — dropping scaffolding-only scenarios in favor of real end-to-end tests as SDK surface lands. |
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.
Summary
server-initiated-request-formatscenario from Sendspin/conformance#59 to the matrixstream-request-format-emiton the aiosendspin server onlyNotes
stream/request-format, so every client case fails fast — this is exactly the dead-protocol-surface signal the audit asks the harness to surface.Test plan
python -m compileall src scriptspython -m conformance.cli run --results-dir results --from aiosendspin --to aiosendspin --timeout-seconds 25shows the new scenario row with the expected fail-fast reason