From 9dfcddf40be49f5f9d81b639c380a7d54fb58f6f Mon Sep 17 00:00:00 2001 From: Hare Date: Sat, 1 Aug 2026 17:24:10 +0900 Subject: [PATCH] docs: report spawned worker launcher mismatch --- ...wn-worker-runtime-cli-mismatch-20260730.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/report/spawn-worker-runtime-cli-mismatch-20260730.md diff --git a/docs/report/spawn-worker-runtime-cli-mismatch-20260730.md b/docs/report/spawn-worker-runtime-cli-mismatch-20260730.md new file mode 100644 index 00000000..869798eb --- /dev/null +++ b/docs/report/spawn-worker-runtime-cli-mismatch-20260730.md @@ -0,0 +1,25 @@ +# SpawnWorker fails against current `yoi-runtime` CLI + +Date: 2026-07-30 + +## Symptom + +A `SpawnWorker` tool call failed before creating its socket. The child process stderr was: + +```text +yoi-runtime: unexpected positional argument `worker` + +Usage: yoi-runtime [OPTIONS] +``` + +The Worker-management layer appears to invoke the configured Runtime executable with a legacy positional `worker` subcommand, while the current `yoi-runtime` binary starts the Runtime HTTP service directly and no longer accepts that subcommand. + +## Impact + +Read-only review delegation was unavailable during the Workspace credential repair implementation. Work had to continue in the parent Worker without a spawned reviewer. + +## Suggested investigation + +- Check the SpawnWorker process launcher command construction against the current `yoi-runtime` CLI contract. +- Ensure runtime executable discovery does not select the server binary when a dedicated Worker child executable/protocol entrypoint is required. +- Add an integration test that starts a spawned Worker through the same command used by the Worker-management tool and waits for its socket.