Case

aiosendspin -> sendspin-js

Start the server first, then the client. The client advertises a listener and PCM as its only supported audio format, the server connects in and streams audio derived from almost_silent.flac, and both adapters record each audio frame as it crossed the transport. The matrix verifies that every frame is message type 4 behind the 13-byte header (type, int64 timestamp, uint32 send_ahead), that the client read the same 13 bytes off each one, and that no chunk lasted longer than 150 ms or, the final chunk aside, less than 15 ms. This test does not compare the audio, and does not judge send_ahead saturation, which no adapter can observe.

Server

aiosendspin

Client

sendspin-js

Status

Failed

Server sent a header of 9 bytes on 199 of 199 audio chunks; roles/player/v1.md requires 13 bytes (type, int64 timestamp, uint32 send_ahead); server adapter reported: aiosendspin classified the client/hello as older than send_ahead (unencrypted, a trust_level key, or player supported_commands in client/hello) and kept the header without it for that client

Server activation

Initial server/activate

What the aiosendspin server's own adapter recorded for its first server/activate on this connection, reported as sent. The case fails when none was sent, when its activities are not unique values from playback and pairing, or when it omits active_roles. Nothing else in it is checked against the specification: which activities and roles the matched PSK allows is not judged. A recording that cannot be read as that message is shown whole and not judged either.

activitiesplayback
active_rolesplayer@v1controller@v1metadata@v1

Server group state

Every group/update after activation

What the aiosendspin server's own adapter recorded for each group/update it sent after its first server/activate on this connection, in order and reported as sent. The case fails when none followed, or when in any of them playback_state is not playing or stopped, or group_id or group_name is missing or not a string. How soon the first followed is not judged, because the specification says promptly and gives no bound, so one sent at any point in the case counts. Whether a change to a field produced a further message is not judged either. A recording of anything other than that message is shown whole and fails the case as a harness gap.

1 of 3

playback_state"stopped"
group_id"36bc1d8a-bbf4-4329-818b-7ea6520b73f4"
group_name"sendspin-js-client"

2 of 3

playback_state"playing"
group_id"36bc1d8a-bbf4-4329-818b-7ea6520b73f4"
group_name"sendspin-js-client"

3 of 3

playback_state"stopped"
group_id"36bc1d8a-bbf4-4329-818b-7ea6520b73f4"
group_name"sendspin-js-client"

Inspection

Summaries, logs, and builds

Matrix result

RAW
{
  "case_dir": "artifacts/results/data/macos__server-initiated-audio-chunk-framing__aiosendspin__to__sendspin-js",
  "client_exit_code": 0,
  "client_impl": "sendspin-js",
  "reason": "Server sent a header of 9 bytes on 199 of 199 audio chunks; roles/player/v1.md requires 13 bytes (type, int64 timestamp, uint32 send_ahead); server adapter reported: aiosendspin classified the client/hello as older than send_ahead (unencrypted, a trust_level key, or player supported_commands in client/hello) and kept the header without it for that client",
  "scenario_id": "server-initiated-audio-chunk-framing",
  "scenario_revision": 4,
  "server_exit_code": 0,
  "server_impl": "aiosendspin",
  "status": "failed",
  "unsupported": false
}