Docker lane flake: the_hermes_image's "run: fragment list --json" comes back [Command interrupted] (exit 130) #776

Seen on #752's CI (run 41144150820, docker (real Hermes)). #753 is stacked on it with byte-identical images/ code, and its Docker lane passed.

What failed: images/bridge/tests/docker.rs:590. The chat says run: fragment list --json, and the scripted model's tool call runs it in Hermes' terminal. The reply was:

scripted: the tool said: {"output": "[Command interrupted]", "exit_code": 130, "error": null}

so the assertion that the reply lists paul's fragments (skills--k3x9, talk--k3x9) failed. Exit 130 is an interrupt (SIGINT): Hermes stopped the command before it answered.

Also in the log, earlier: two other scripted-model calls in the run failed with 500 provider_failed: the scripted model is unavailable (Hermes retries once, attempt 1/1). They may be unrelated.

Not yet known: what interrupted the terminal command: a second delivery into the same chat, a stop, or a terminal timeout under CI load.

Not touched by the session-archive stack's bridge change (note.rs/driver.rs: a history note on TurnStart). Filed so the class can be root-caused rather than rerun. Related: #614 (another real-Hermes Docker-lane flake).