Leave the next command where the build will find it

The kernel build has forty minutes left and you have a train to catch. You don't wait, and you don't type the deploy command into a session where it would land in the compiler's output.

You POST it to the terminal's execute endpoint with defer_pid set to the build's process ID and defer_timeout_ms long enough to cover it. The API returns immediately. The command sits parked, and when that PID exits it runs in the same shell, same working directory, same environment. It waits for the process, not for a prompt that looks free. A start-time check guards against the PID being reused by something else.

The build finishes at 4:12. The deploy starts at 4:12. You are on the train.

You don't wait for the build; you leave the next command where the build will find it.