Cloud: update outdated machines before opening no-folder chats
Leo asked for no-project Cloud chats to start immediately: “I want us to be able to do this too.”
When a Cloud chat had no folder and its selected machine was running an older cmux-tui, startup attempted to open the chat tab before updating the machine. The daemon lacked agent-session-tabs-v1, so the start failed with the existing unsupported-machine refusal.
This change reuses the package-level Cloud outdated-machine relink wait before opening a chat tab. If the machine does not advertise the capability, Cloud updates it, waits up to 90 seconds for the new handshake, and then lets the existing tab-opening path re-anchor and perform its normal capability check. Folder and no-folder starts share this path. If the update cannot complete or times out, the existing refusal remains. Package tests cover update-and-capability arrival, bounded relink timeout, and already-current machines.
Validation: python3 scripts/cmux-next/prepush-gate.py
agent-identity footer --repo manaflow-ai/cmux
Agent session: agent session