Case

sendspin-go -> sendspin-jvm

Start the server first, then the client. The client advertises a listener, the server connects in, observes controller state, receives a control command, disconnects, and the matrix verifies the recorded command.

Server

sendspin-go

Client

sendspin-jvm

Status

Passed

Controller command matched (next)

Inspection

Summaries, logs, and builds

Matrix result

RAW
{
  "case_dir": "artifacts/results/data/macos__server-initiated-controller__sendspin-go__to__sendspin-jvm",
  "client_exit_code": 0,
  "client_impl": "sendspin-jvm",
  "reason": "Controller command matched (next)",
  "scenario_id": "server-initiated-controller",
  "server_exit_code": 0,
  "server_impl": "sendspin-go",
  "status": "passed"
}