Cloud VM image: pin cmux-tui f7b9c571 (a clock sync is not a resume, #35193)
Pins the Cloud VM image lock's cmux-tui and cmux-tui-hook to the published build of f7b9c571, the merge of #35193. Without it, cmux-host read every clock set by the provider as a resume. The provider sets the guest clock on each exec and file operation, so each one dropped the Native receiver (UDP 4101) for 15 to 30 s. A new Cloud chat's identify kept missing the receiver, and the start gave up with "didn't connect".
Generated with bun images/cmux-vm/pin-cmux-tui.ts --commit f7b9c57198dcea5e5949e81c23ef09b000a247ce --write. The sha256 and size come from the build's manifest (https://github.com/manaflow-ai/cmux/actions/runs/41809039490). Only the two lock entries change. f7b9c571 is on feat-cmux-next after 0ae14130 (the current pin), so it keeps everything the current pin has.
Checked on a development machine with this build installed (the probe's machine.install): six execs over 2.5 minutes, UDP 4101 listening at every check, one receiver process the whole time, and no Resumed after the install. On the current image, the same probe found 4101 down at 7 of 8 checks.
After this merges: a kept native_receiver bake, its image in workers/cmux-vm staging VM_BOOT_IMAGES, then cmux-platform development and staging CLOUD_VM_API_IMAGE switched to it.
Risk: image input only. Nothing boots it until those steps.
Changelog
none
Agent session: agent session
🤖 Generated with Claude Code
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Pins cmux-tui and cmux-tui-hook in the Cloud VM image lock to f7b9c571, the merge of #35193, so the VM stops treating a provider clock set as a resume.
cmux-host previously read every clock set by the provider as a resume, dropping the Native receiver (UDP 4101) for 15 to 30 s. The provider sets the guest clock on each exec and file operation, so a new Cloud chat's identify kept missing the receiver, and the start gave up with "didn't connect". Only the two lock entries change; f7b9c571 keeps everything the current pin 0ae14130 has. After merge, a kept native_receiver bake and its image in workers/cmux-vm staging VM_BOOT_IMAGES are needed before cmux-platform development and staging CLOUD_VM_API_IMAGE can switch to it. Risk is image input only, nothing boots it before those steps.