opencode run --session <uuid>: silent exit with no output, no error (exit 0)

[seva]

Summary

When opencode run is invoked with --session <uuid> (plain UUID, not OpenCode's ses_... format), the process exits silently — no stdout, no stderr, exit code 0.

Steps to reproduce

opencode run --model <any-model> --session "a1b2c3d4-e5f6-7890-abcd-ef1234567890" "reply ALIVE"

Expected behavior

Either reject the invalid format with an error, or create a new session and proceed.

Actual behavior

• stdout: empty
• stderr: empty
• exit code: 0
• completes in ~2.6 seconds

Contrast: ses_... format with missing session

NotFoundError: Session not found: ses_nonexistentfake123

The ses_... case at least errors. The UUID case is completely silent.

Impact

Silent failure is indistinguishable from a successful empty response. Any subprocess caller that passes its own UUID-format session IDs will receive no output and no indication of failure.

Environment

• Platform: Windows
• Invocation: subprocess (piped stdout/stderr)