Add server-initiated-drift-injection scenario (#57)#65
Closed
balloob wants to merge 1 commit into
Closed
Conversation
Adds the drift-injection scenario from the audit (#57) and a `required_capability` mechanism on `ScenarioSpec` so scenarios can gate matrix participation on SDK-side surface area. The matching `supported_capabilities` tuple on `RoleSpec` lets each adapter declare which named capabilities it implements. - `stream-sync-drift-correction` is declared on the aiosendspin server (it can host the harness-level timestamp skew) and on no client. All client cases fail fast with a clear "does not expose the capability" reason, which is exactly the conformance signal the audit wants surfaced. The verification mode is `capability-only` until SDK implementations land and the test can compare recovered audio against a tolerance derived from the spec thresholds. This is the first of eight stacked PRs that wire the audit's recommended scenarios into the matrix.
This was referenced May 27, 2026
Collaborator
Author
|
Closing per discussion: the capability mechanism only existed to power capability-only fail-fast paths for scenarios where no SDK currently exposes the surface. Per #68 we are landing only the real end-to-end test (24-bit PCM) and dropping the scaffolding PRs. The other scenarios will be revisited when SDKs grow the necessary surface. |
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-drift-injectionscenario from Sendspin/conformance#57 to the matrixrequired_capabilityfield onScenarioSpecand a matchingsupported_capabilitiestuple onRoleSpecso scenarios can gate matrix participation on SDK-side surface areastream-sync-drift-correctionon the aiosendspin server (which can host the harness-level timestamp skew); declares it on no client, so every client fails fast with a clear "does not expose the capability" reason — that is the conformance signal the audit asks forNotes
capability-onlyuntil SDK-side drift correction lands in some client adapter; the test can then compare recovered audio against a tolerance derived from the spec's soft/hard correction thresholds.RoleSpec.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