xversion drive() types with zero settle after dial; cold containers can lose the line

open   by a73x

First xversion run of the day (cold podman vfs store) failed legs 1-2: client exits 0 but the old daemon's grid never got the typed printf line, both transports. Host repro of the same binary pairing passes deterministically; container re-run passes 10/10. drive() pipes the command into mux stdin the instant the process starts — nothing waits for the attach/claim to land before typing, so a slow first container start can lose the race. Harness robustness, not a compat bug: consider an expect-on-first-paint (or short poll of muxd dump for the prompt) before typing, like e2e's settle. Seen 2026-08-25 on v0.0.1-13 vs v0.0.1-5.

Comments

2026-08-29: drive() unchanged — printf | sleep 2 | ^\^\ with no settle after the dial (test/xversion.sh:154).