#35530 Cloud VM image: pin cmux-tui b1f8fc4d (receiver lease renewal #35467, person-prompt activity #35476)

Pins the Cloud VM image lock's cmux-tui and cmux-tui-hook to the published build of b1f8fc4d, the merge of #35476 on feat-cmux-next. Over the current pin (f7b9c571, #35259) it adds:

• #35467: the Native receiver renews its receiving policy ahead of the lease end by its measured read time, and accepts leases up to 120 s. Without it a Cloud chat drops about every 27 s when a policy read is slow, and cmux-platform#812 cannot raise the lease cap.
• #35476: acpmux reports when a person last prompted a chat (last_person_prompt_at), for the post-chat warm window.

Generated with bun images/cmux-vm/pin-cmux-tui.ts --commit b1f8fc4d83eac93615caa8e5ccfe0d92ad71426b --write. The sha256 and size come from the build's manifest (https://github.com/manaflow-ai/cmux/actions/runs/41847723856). Only the two lock entries change. b1f8fc4d is on feat-cmux-next after f7b9c571, so it keeps #35193 (a clock sync is not a resume).

After this merges: a kept native_receiver bake from the merge, its image in workers/cmux-vm staging and production VM_BOOT_IMAGES, then cmux-platform CLOUD_VM_API_IMAGE moved to it (development and staging first, production once the staging journey reads a reply). Production today still boots cloud-native-5e57723, which lacks #35193, so its journey fails at connect ("the original receiving VM has no live ready attempt").

Risk: image input only. Nothing boots it until those steps.

Changelog

none

Agent session: agent session

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Pins the Cloud VM image's cmux-tui and cmux-tui-hook lock entries to the b1f8fc4d build, replacing the f7b9c571 pin.

• Adds receiver lease renewal (#35467), so Cloud chats stop dropping about every 27 seconds when a policy read is slow.
• Adds last_person_prompt_at reporting from acpmux (#35476) for the post-chat warm window.
• Only the two lock entries change; the sha256 and size come from the new build's manifest.
• Nothing boots this image until the bake and VM image rollout follow-up; production today still boots an older image.