Skip to content

Add server-initiated-static-delay scenario (#63)#71

Closed
balloob wants to merge 1 commit into
claude/conformance-multi-serverfrom
claude/conformance-static-delay
Closed

Add server-initiated-static-delay scenario (#63)#71
balloob wants to merge 1 commit into
claude/conformance-multi-serverfrom
claude/conformance-static-delay

Conversation

@balloob
Copy link
Copy Markdown
Collaborator

@balloob balloob commented May 27, 2026

Summary

Notes

Test plan

  • python -m compileall src scripts
  • python -m conformance.cli run --results-dir results --from aiosendspin --to aiosendspin --timeout-seconds 25 shows the new scenario row with the expected fail-fast reason

Adds the static-delay measurement scenario from
#63. Per the audit, the highest-severity bug in
the survey is the "parse-but-ignore" failure mode: sendspin-rs and
SendspinKit parse `static_delay_ms` from the protocol but never apply
it in the playback path. Seven SDKs additionally don't persist the
value across restarts.

`static-delay-applied` is declared on the aiosendspin server only.
Every client case fails fast until each adapter declares the
capability based on the SDK's exposed surface.
@balloob
Copy link
Copy Markdown
Collaborator Author

balloob commented May 27, 2026

Closing per discussion in #68 — dropping scaffolding-only scenarios in favor of real end-to-end tests as SDK surface lands.

@balloob balloob closed this May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant