Repository navigation
PR watch has merged nothing since 15:57 UTC; #699 (fleet host AMI) is ready and waiting #700
Description
#699 has been ready since 16:18 UTC 2026-10-26, its head is Codex-reviewed with no findings, CI is green and it is mergeable, but the jumpbox PR watch has not merged or commented on it; the last merged PR is #698 at 15:57 UTC. #699 moves fcvm_fleet_host_amis (us-east-1) to ami-00d8ecc3edfb8059e, built from ejc3/fcvm main 2c965afe: routed GPU guests get IPv6 NTP servers (ejc3/fcvm#1343) and the IPv4 slot-port relay sets TCP_NODELAY (ejc3/fcvm#1350). Both close the remaining lag of the staging wall's fcvm tiles behind its EC2 tiles. Needed: the watch to take #699 (merge and apply).
Activity
ejc3 commentedon Oct 27, 2026
PR #699 is merged as 79305d1 and applied. The follow-up full Terraform plan reports No changes, and /infra/applied-status is clean. New host launches use the updated AMI; running hosts were not recycled.
The recurring watch did not stop because its job expired: its scheduler fired 19 times after the last successful run, and each turn returned HTTP 429 usage_limit_reached before any tool call. This manual Codex run completed the merge/apply, but did not restore model capacity for the recurring Claude session. Leaving this issue open for that remaining automation gap.