“Started” is not
the same as “done”.

When an assistant runs a command, there are several different claims it might make. A process was created. Output appeared. The process exited. The intended task succeeded. Only the last one answers your original request.

Start once, then poll

Ganado Bridge returns a session identifier when a process starts. The assistant reads that session with a byte offset to collect subsequent output. It should not start the same command again merely because a previous call returned before completion. This is especially important for commands that write files or perform a deployment.

Inspect the final state

Look for an exited state and the actual exit code. A running process is not a successful process. A timeout is not a clean completion. If output was truncated, the response should say so rather than implying a complete review.

Verify the task’s outcome

Exit code zero means the command reported success; it does not prove the business outcome. A deployment may still point the wrong alias at the wrong version. A backup command may produce a file that has never been restored. Choose an independent check suited to the task: an expected file, a health response, a revision identifier or a restore test.

Keep host identity explicit

Before acting on a remote system, confirm the local connection and the intended SSH alias. The file tools operate locally. A command should name a configured remote target when needed. Do not infer that a familiar-looking path belongs to the expected host.

Know where continuity ends

Bridge sessions survive separate tool calls, not an agent restart. A sleeping Mac cannot execute new calls. Stopping the local SSH client also does not certify that every remote child process stopped. Inspect the remote state separately when that matters.

A better completion receipt

Host: the intended authorized machine
Action: the command actually run
Process: exited, with the actual exit code
Evidence: the relevant output or resulting artifact
Limits: timeout, truncation or checks not performed
Outcome: verified separately where needed

These distinctions are the point of the product: less copying, without replacing evidence with confidence.