Case

sendspin-go -> sendspin-js

Start the server first, then the client. The client advertises a listener, the server connects in, sends a metadata state update, disconnects, and the matrix compares a normalized metadata snapshot.

Server

sendspin-go

Client

sendspin-js

Status

Passed

Metadata snapshot matches

Inspection

Summaries, logs, and builds

Matrix result

RAW
{
  "case_dir": "artifacts/results/data/macos__server-initiated-metadata__sendspin-go__to__sendspin-js",
  "client_exit_code": 0,
  "client_impl": "sendspin-js",
  "reason": "Metadata snapshot matches",
  "scenario_id": "server-initiated-metadata",
  "server_exit_code": 0,
  "server_impl": "sendspin-go",
  "status": "passed"
}