Repository navigation
fcvm-fleet staging: apply queue for 2026-10-27 (#711 supersedes #708 and #710) #712
Description
The watch has merged nothing since 05:35 UTC. These are ready, in apply order:
- fcvm-fleet: host and tile AMIs from ejc3/fcvm main ce08eee9 (renderer keeps every tile inside its slot) #711: host and tile AMIs from ejc3/fcvm main ce08eee9. It supersedes fcvm-fleet: host and tile AMIs from ejc3/fcvm main 2e2181cf #708 and fcvm-fleet: host AMI from ejc3/fcvm main e15f9e7e (agent snapshot baked, launch files prefetched) #710, which can be closed unmerged. Its images carry:
- renderer: write a VUI bitstream_restriction so decoders do not hold frames fcvm#1361: the renderer writes the H.264 bitstream restriction (decode 234-268 ms down to 1-2 ms per tile in Chrome on macOS);
- Restore steps the guest clock to a host reading taken right before the step fcvm#1382: a restored guest re-reads the host clock right before stepping (a 3 s restore stall left the clone 3 s behind; now within the host bracket);
- the renderer keeping every tile inside its frame slot (one slow tile held the whole wall at about 19 fps).
- fcvm-fleet: check viewer words with Claude Haiku 5.5 on Bedrock #707: Bedrock Haiku text check for viewer words. Staging refuses every word until it is applied ("no text check is configured").
- Mac: DerivedData and simulator devices on the scratch drive #709: Mac scratch-drive paths (unrelated to the fleet).
After #711 applies, the fleet must sleep and wake (10 minutes with no viewer) for the hosts to start from the new image.
Activity
ejc3 commentedon Oct 27, 2026
Completed the apply queue via the repository's PR-watch workflow: #711, #707 and #709 are merged and applied; #708 and #710 are closed as superseded. The full Terraform follow-up is empty at e4e019d.
Coordinator revision 45 is running with the Bedrock word-check flags, a completed rollout and healthy DNS target. Actual-role IAM checks and a separate exact-prompt model smoke test passed after fleet-account model activation. All four latest launch templates contain the new AMIs, and the deployed coordinator selects $Latest. Existing hosts pick up those images through subsequent launches, including the normal idle sleep/wake cycle; no forced host recycle was performed. The Mac scratch setup was already correct and was verified read-only.
Closing the completed merge/apply queue. The recurring watch quota issue remains tracked separately in #700.