rdmpw3275m changelog — Tyrell r3 containment and r4 coordination

Detected the Build 20 r3 canary's closed-lid control failure, preserved evidence, coordinated exact rollback and r4 preparation on the canary, updated canonical tickets/receipts, and retargeted the durable heartbeat to the prepared r4 launch gate.

Scope

• Coordinator host changed: rdmpw3275m.
• Remote operational host changed: rdmbair15m5, separately recorded in its host changelog.
• Canonical evidence host changed additively: rdmsm4x handoff and issue comments; no source or Git state changed.

Exact local files and state changed

• Created local evidence directory /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build20-canary-r3-lid-closure-20260912-2118.
• Created local r4 preparation directory /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build20-canary-r4-prep-20260912-96a5fc0.
• Updated heartbeat automation finish-tyrell-build-16 in place to track r3 rollback, the physical open-lid gate, and prepared r4.
• Automation TOML SHA-256 after update: 19eae67185566af42119e6b9386afd3c79133f63f81e251cceb099884c155ec9.
• Added canonical receipts under /Users/richh/dev/_handoff/tyrell-build20-memory-20260912/canary-r3-lid-closure and canary-r4-prepared on rdmsm4x.
• Appended evidence comments to ISSUE-20260912-14, TASK-20260911-01, and ISSUE-20260912-01.

Commands and operations

• Ran agentkit preflight, fleet mailbox sync, held-ticket checks, and both Tyrell and local-agy evidence checks.
• Used read-only SSH checks to confirm the failed clamshell assertion and healthy pre-containment candidate.
• Preserved raw r3 samples, inventory, state, policy, guard, and rollback logs before and after bounded rollback.
• Patched only the isolated r4 harness copy, tested it, staged it on the canary, and prepared rollback state without installing or launching Build 20.
• Copied evidence to canonical handoff paths and sent a high-priority fleet-bus milestone to the canonical owners.
• Updated the existing heartbeat via its supported automation control plane; schedule, target task, and notification policy were preserved.

Verification evidence

• Canonical r3 receipt SHA-256: ee93a95ed7174bbae25786c46e8aa1c64d55b12c9305a45db390c5424ad333f0.
• Preserved r3 sample-history SHA-256: fb83aecafef75624f0bdae4f63bad2c667be8ddd0775013cd75075c3895b307c.
• Canonical r4 receipt SHA-256: 3586c644285a4bcdca338a1b8043317064f4a4b8953ad7f05a31984f845bbdf1.
• Canonical and local hashes matched after transfer.
• Ticket CLI confirmed all three comments were appended by codex@rdmpw3275m/01a078a7.
• Fleet message ID: 20260912-212606-D6E3B69F; synchronization succeeded to all five peer hosts.
• Local agy manifest and STATUS hashes remained unchanged; agy CLI count stayed zero with no authoritative incomplete or quota-blocked parent.

Backups and undo

• R3 and r4 evidence directories are additive and retained both locally and canonically.
• To undo the heartbeat change, use the automation control plane to replace its prompt while preserving ID, schedule, task target, notification policy, and active status; do not edit TOML directly.
• Tyrell is already on its verified exact rollback. The r4 stage has not changed installed product state.

Outstanding actions

• Physical owner action is required to open rdmbair15m5 on AC before r4 may install or launch.
• Continue the active heartbeat; after launch, rerun every acceptance clock from zero and prohibit fleet expansion until all gates finish.
• Continue waiting for explicit canonical agy handoff receipts; do not launch agy without authoritative incomplete-parent or real provider-quota evidence.