v0.58.0 — a silent hand-off says so

A hand-off that runs nothing no longer looks like a clean session

/agents deepseek printed this, and it read as success:

· opening deepseek autonomously — hand-off to its CLI, exit it to come back…
· deepseek exited (code 0). back in the pit.

The engine had not run a single line. "exited (code 0)" is what the pit says
when somebody opens an agent and quits it, so the failure was invisible and the
search for the bug started in the wrong program.

It is a real failure mode rather than a hypothetical. @serjm/deepseek-code
0.5.0 decides whether it is the entrypoint by comparing
resolve(process.argv[1]) against import.meta.url, and npm installs every
global bin as a symlink — so the comparison never matches, the program falls off
the end having done nothing, and exits 0. Anyone who installed it the documented
way got a CLI that silently does nothing. (A fix is open upstream.)

The child owns the terminal while it runs, so its output is not the pit's to
inspect. The clock is enough: an exit of 0 in under a second and a half did not
host a session anybody used, and the pit now says so —

· deepseek exited (code 0). back in the pit.
⚠ deepseek exited instantly without running — that usually means a broken
  install, not a clean session. check it directly with `deepseek-code
  --version`, and reinstall with /install deepseek if that prints nothing.

Only for silent success. A non-zero exit already says something went wrong, and
the engine has usually printed why; adding "that was fast" on top would be
noise. Workflow-tool hand-offs get the same treatment, because they fail the
same way.