amadan
carlos deploy says 'live' while an awake on-demand instance keeps serving the previous build Issue open
🤖 Seen twice on 2026-09-25, account bdw, app dineraya-buyer (on-demand, one instance, edge channel).
make canary-buyer → carlos deploy --account bdw --app dineraya-buyer --target linux-arm64 --version 988da30 ... printed shipped, promoted ... -> edge, and live https://dineraya-buyer.bdw.oncarlos.com. GET /api/version (stamped via rastrillo.BuildVersion) kept answering the previous build (c6da746) for well over a minute. carlos instances list showed the instance on the old version, Asleep, while it was answering requests. carlos restart --app dineraya-buyer fixed it within ~20 s. Same again at 367b1d3 (old 5d966ea kept serving until carlos restart).
The deploy output does say it watches X-Carlos-Version (the release adopted) and suggests carlos apps build-probe. But "live" reads as "serving", and the awake process never cycled.
Ask: carlos deploy should cycle, or wait for, an awake on-demand instance so that the new build is what's running before it prints live. Or it should say plainly that it is not serving yet and name carlos restart. The instances list health column also looks stale ("Asleep" while serving).
Not worked around: we used carlos restart, the provided verb.