When an agent does not respond, internal/job/client/client.go:502 records Status: StatusFailed with the error text timeout: agent did not respond. The job status enum has no timeout value and the SDK does not handle that string, so callers cannot tell "never responded" from "ran and failed".
Fix: add a timeout status (or structured error code) and surface it through the SDK and the domain broadcast responses.
Found in the September 2026 codebase review. Tracked in the review tracking issue.
When an agent does not respond,
internal/job/client/client.go:502recordsStatus: StatusFailedwith the error texttimeout: agent did not respond. The job status enum has no timeout value and the SDK does not handle that string, so callers cannot tell "never responded" from "ran and failed".Fix: add a timeout status (or structured error code) and surface it through the SDK and the domain broadcast responses.
Found in the September 2026 codebase review. Tracked in the review tracking issue.