Skip to content

Add server-initiated-external-source scenario (#61)#69

Closed
balloob wants to merge 1 commit into
claude/conformance-24bit-pcmfrom
claude/conformance-external-source
Closed

Add server-initiated-external-source scenario (#61)#69
balloob wants to merge 1 commit into
claude/conformance-24bit-pcmfrom
claude/conformance-external-source

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 external-source group-swap scenario from
#61. Per the audit, only SendspinKit exposes a
client-side `enterExternalSource()` / `exitExternalSource()` API
today; every other client SDK has no embedder-facing handle. The
aiosendspin server already handles the full external-source group
flow (`server/roles/controller/v1.py:93-119`).

`external-source-client-api` 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