A short, human-readable label for that step, supplied by the API — e.g.
"Robo guardian image pulled". The API owns the wording and may change
it, so never branch on it.
Whether the API considers this the last step of a successful setup.
Means "the script's final report arrived", not "the robos are up": the container starts moments before this is sent, and its guardians have not reached the relay yet.
The organisation whose host reported the step.
Which step the host reported, starting at 0.
Good for ordering, de-duping a replay, or a "step N" label. Not for detecting the end: the API does not say how many steps there are, so there is nothing to compare against. Use final.
A robo host's setup-progress update, pushed to the host owner's user socket each time the provisioning script reports a completed step.
Advisory only — nothing in the SDK gates on these. Three things make them lossy, and none are fixable client-side:
0.So an update can be missed or seen twice, and no sequence of them tells you a host is ready. Use RoboHost.waitUntilOnline for that. This is the canonical statement of the caveat; other doc comments point here.