Problem
spawn_system_binary currently prints [ OK ] immediately after Command::spawn. The boot loop sleeps for 1.5 seconds but does not call try_wait for normal built-ins before continuing.
The preliminary benchmark captured Pilot exiting immediately with:
error: unexpected argument '-S' found
Boot still reported Pilot as up, and SubmitTask later timed out waiting for gRPC.
Acceptance criteria
- Do not print
[ OK ] for a built-in until it survives the startup grace period.
- If the process exits during startup, boot fails immediately, names the component and exit status, and points to its log.
- Partial bring-up is torn down through the existing failure path.
- A regression test launches an immediate non-zero exit and proves boot rejects it.
- A live built-in still produces the existing concise success line after the check.
This was one runtime failure in a preliminary first-12 benchmark run. Robonix is under active optimization, and these results do not represent final system performance.
Problem
spawn_system_binarycurrently prints[ OK ]immediately afterCommand::spawn. The boot loop sleeps for 1.5 seconds but does not calltry_waitfor normal built-ins before continuing.The preliminary benchmark captured Pilot exiting immediately with:
Boot still reported Pilot as up, and
SubmitTasklater timed out waiting for gRPC.Acceptance criteria
[ OK ]for a built-in until it survives the startup grace period.