rdmpw3275m changelog — Tyrell heartbeat r3 refresh

Updated the existing Tyrell/agy recovery heartbeat so future runs follow the active Build 20 r3 canary rather than the superseded first canary attempt; this prevents stale PID, stage, and acceptance-window data from driving recovery decisions.

Scope

• Changed host: rdmpw3275m only.
• Monitored canary host: rdmbair15m5; this update did not change its application, daemon, database, or guard.
• Canonical source host: rdmsm4x; this update did not change source or Git state there.

Exact state changed

• Updated Codex heartbeat automation finish-tyrell-build-16 in place.
• Local automation record: /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml.
• Post-update SHA-256: fd8c839abba28839a63c94d1ec2a5ac791315b96deb92427f9b1f9b358dc6a58.
• Schedule, active status, target task, and notification policy were preserved.
• Prompt now records the r1/r2 sleep interruptions, active r3 stage and exact identities, the passed short gate, pending six-hour and 24-hour gates, rollback requirements, and unchanged local agy supervision rules.

Commands and operations

• Ran mandatory agentkit preflight and fleet mailbox synchronization.
• Independently inspected the r3 guard, samples, inventory, launchd process, exact artifact hashes, stable daemon link, API status planes, SQLite integrity/schema, and power assertions over SSH.
• Inspected the existing automation TOML and updated the existing automation through the Codex automation control plane.
• No source build, install, service restart, database write, rollout, ticket ownership transfer, or agy launch occurred.

Verification evidence

• Automation control plane returned Updated automation in the app for ID finish-tyrell-build-16, status ACTIVE.
• Local automation TOML re-read after update and hashed as recorded above.
• At 2026-09-12 20:38 EDT, r3 guard PID 24726, assertion PID 24750, and daemon PID 24853 were alive; both sleep assertions were bound to the guard; power was AC and clamshell open.
• Stable daemon link resolved to the exact Build 20 release; daemon SHA-256 71bf6122e453315205f3f0dfaf3f1a3a6cf2d99dfe901cda88e7ac79a8112c77 and app executable SHA-256 423871cede8ae6313c486929f544dbee8d1085540b2d37896de6f2c2d4de90fd matched.
• Launchd reported runs=1 and never exited; both status planes returned HTTP 200 with valid JSON; SQLite quick_check returned ok with one additive last_seen_at column.
• Seventy-six samples spanned 4500.528905 seconds with maximum gap 60.063863 seconds; inventory passes 1 and 2 were unchanged; no failure, rollback, long-gate, or 24-hour artifact existed.
• Local agy manifest and STATUS hashes were unchanged, exact agy CLI process count was zero, and no eligible incomplete or quota-blocked parent appeared.

Backup and undo

• The automation was updated in place by its supported control plane; no separate filesystem backup was created.
• To undo, update automation finish-tyrell-build-16 through the same control plane with the preceding prompt while preserving its schedule, target task, notification policy, and ACTIVE status. Do not edit the TOML directly.
• Tyrell rollback remains the exact signed Build 15 daemon plus Build 17 app described in the canonical Build 20 handoff; no rollback was needed by this update.

Outstanding work

• Keep the r3 canary isolated until the six-hour-after-warmup gate at or after 2026-09-13 01:35:24 EDT, the fixed 24-hour endpoint at 2026-09-13 19:25:24 EDT, a fresh app probe, and a controlled reboot proof all pass.
• Continue waiting for explicit canonical agy handoff receipts; resume an agy parent only if authoritative state proves it incomplete and, for quota, only after a real provider reset boundary.