Tyrell Build 26 R4 six-hour pass and AC-envelope rollback

Tyrell Build 26 R4 independently passed its same-process six-hour physical-footprint gate on rdmbair15m5, then left the required AC-power envelope and automatically restored the exact prior Build 17 app and Build 15 daemon. DEC-20260916-04 makes the six-hour result the Build 26 acceptance boundary and supersedes a further laptop soak. The accepted Build 26 app and daemon were therefore reinstalled on the canary and independently verified exact and healthy on all six fleet hosts.

Scope

• Coordinator and changelog host: rdmpw3275m.
• Canary host: rdmbair15m5.
• Canonical evidence host: rdmsm4x.
• Product source and the Build 26 release branch were not changed.
• Runtime mutations were the pre-existing guard's policy-required automatic rollback after AC loss and the subsequent owner-authorized reinstall of the already accepted Build 26 artifact on rdmbair15m5.
• Local AGY work remains terminal or safely contained. No AGY process or conversation was resumed, and no provider quota-reset event occurred.

Six-hour result

• Candidate daemon PID 78205, started Thu Sep 17 01:57:52 2026.
• Candidate daemon SHA-256 a4f43d83eb69113ed05d22b8f0b8521e09f71cd3475857e21d89e2572efea6e4.
• Candidate app executable SHA-256 75d41b417c393fb71ee9483836dcf1397236f207a2919faeabb3e74e9c1e9d2c.
• Gate passed at 2026-09-17 08:07:59 EDT.
• 361 samples spanning 21604.068165063858 seconds.
• Ending physical footprint 22.782508850097656 MiB.
• Endpoint growth -0.005858208081089449 MiB/min.
• Least-squares slope 0.09757104885877113 MiB/min versus the unchanged 0.20 limit.
• Ending RSS 522.71875 MiB, diagnostic only.
• Inventory passes 1 through 7 completed with an unchanged repeat.
• Maximum frozen-history sample gap 60.24330186843872 seconds.
• Descriptor range 26 through 30.
• TCP baseline/minimum/maximum 2/2/3, with one single-sample excursion that returned to baseline.
• Guard-owned assertion PID 78091, AC power, closed clamshell, exact process identity, both HTTP status planes, and database integrity held throughout the candidate sample history.
• Independent verifier exited zero and matched the saved long-gate receipt.

Environmental abort and automatic rollback

• AC-envelope departure recorded at 2026-09-17 08:15:07 EDT.
• Terminal R4 state: rolled_back with reason canary left AC power envelope.
• Interlock disarmed and the normal LaunchAgent was re-enabled.
• Candidate daemon, guard, allocation sidecar, and guard-owned assertion processes were absent after rollback.
• Restored Build 17 app executable SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e.
• Restored Build 15 daemon SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0.
• Restored daemon PID 35780; both APIs returned HTTP 200 with valid JSON and database PRAGMA quick_check returned ok.
• AC had returned by the 08:19 EDT post-rollback check. The interrupted 24-hour laptop envelope remains environmental-inconclusive as evidence, but it is not a Build 26 release blocker because DEC-20260916-04 superseded it and the owner explicitly accepted the six-hour pass.

Accepted reinstall and fleet verification

• Reinstalled the retained, signed and notarized Build 26 app on rdmbair15m5 at 08:27 EDT and repointed its stable managed daemon path to the retained hash-addressed Build 26 release.
• App build 26, executable SHA-256 75d41b417c393fb71ee9483836dcf1397236f207a2919faeabb3e74e9c1e9d2c.
• Daemon SHA-256 a4f43d83eb69113ed05d22b8f0b8521e09f71cd3475857e21d89e2572efea6e4.
• Canary app PID 71126, daemon PID 70872, and menu-bar PID 71205; exactly one of each and a running LaunchAgent whose PID matched the daemon.
• Retained replaced app rollback: /Applications/.tyrell-rollbacks/20260917-082717-2c5ca2a674fe/Tyrell.app.
• rdmsm4x, rdmbair13m5, rdmbair15m5, rdmpw3265m, rdmpw3275m, and jdmbair13m5 all independently matched the exact Build 26 hashes, process counts, and managed daemon target.
• Both status APIs on every host returned valid JSON with the expected role; every database returned PRAGMA quick_check=ok; recovery sentinels and launchd-disable interlocks were absent.
• Canonical reinstall receipt: /Users/richh/dev/_handoff/tyrell-build26-release-20260916/accepted-reinstall-rdmbair15m5-20260917-0828.
• Reinstall receipt manifest SHA-256: 442126f806f91e7598b16c6f267aea98ca7da74299050cabe818e1e517b5669b; all listed files verified on the coordinator, canary, and canonical host.

Immutable evidence

• Canary packet: /Users/richh/.tyrell/verification/tyrell-build26-r4-six-hour-pass-ac-abort-evidence-20260917-0815.
• Coordinator packet: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build26-r4-six-hour-pass-ac-abort-evidence-20260917-0815.
• Canonical packet: /Users/richh/dev/_handoff/tyrell-build26-release-20260916/postdeploy-r4-six-hour-pass-ac-abort-evidence-20260917-0815 on rdmsm4x.
• Snapshot-manifest file SHA-256: 329efbe020f694c662f9ec068759966295ff39f0c6a7c2f7419969a716c67110.
• Deterministic recursive manifest SHA-256: 47c73dc2510e23c756076e57e19fec214a3b487de8efad3f0b941f2e51081d1a.
• Packet census: 100 files, 18 directories, zero symlinks, 156,918,454 bytes.
• Long-gate receipt SHA-256: 6dbff812234bc6de7024cc341ef7424150a7addedd6a5f14d3a9a175c2e26775.
• Frozen samples SHA-256: 2af099aada3b1a074eeadbf6bc88f6d3f2ba06cb73760f62a392046e446c4bce.
• State-at-six-hour SHA-256: 2ea6255490c82b88b1e82a4a9628d8f9e7f6ac90891699d86e112eb5d4f70860.
• Independent verifier output SHA-256: 356780b1f8170459bb11e6ce9725ee9b04b9110b863e17e0e93b893d9d228378.
• Independent verifier tool SHA-256: 4777aa05a9e9b596ff30f38134f09784265708e8c20ad62cd882ef34d905ed97.
• Post-rollback status SHA-256: 58e1b0a5f2723d0ad171d9744642c04c0d5a08ac4b09782529c7d8a2388c37a1.
• All three packets independently passed their snapshot manifests and matched the same recursive manifest result.

Files and coordination state changed

• Created this changelog file under /Users/richh/dev/LLM/Claude/changelogs/ and copied it to the canonical archive on rdmsm4x.
• Appended the exact six-hour-pass, environmental rollback, accepted reinstall, and six-host evidence to ISSUE-20260917-01, then resolved it as not a Build 26 regression.
• Appended the control comparison and accepted six-hour result to canonical allocator/inventory bug ISSUE-20260912-01, which remains open for the pre-existing first-repository-pass retention behavior.
• Updated /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-canary-20260915.json with the accepted gate, rollback, owner decision, final reinstall, fleet verification, and no-R5 boundary, then propagated the check-in through the canonical fleet sync.
• Sent provenance-linked milestone messages to the canary and canonical Tyrell owners.
• Filed the required Apple Notes changelog in folder rdmpw3275m under exact title rdmpw3275m-changelog-20260917-0821-tyrell-r4-six-hour-pass-ac-rollback, record x-coredata://3FF396ED-1AC8-466D-B5F9-AB1CC765F15A/ICNote/p255945; one exact-title match and all three evidence markers were independently verified.

Commands and verification

• Read-only canary inspection with ssh, r4_status.zsh, jq, ps, pmset, launchctl, shasum, HTTP probes, and SQLite PRAGMA quick_check.
• Independent gate recomputation with the frozen verify_r4_gate_v21.py and memory_gate.py.
• Evidence transfer with rsync, followed by shasum -a 256 -c SNAPSHOT-MANIFEST.sha256 and deterministic recursive-manifest verification on all three copies.
• Ticket lifecycle updates through the authoritative ticket proxy on rdmsm4x.
• Fleet coordination through agent_msg.zsh and the canonical check-in sync.

Recovery and undo

• Runtime recovery first completed automatically, and the owner-accepted exact Build 26 app and daemon are now installed and healthy on the canary and all five peers.
• Do not delete or alter the R4 stage or any frozen evidence packet; they are the rollback record.
• Retain /Applications/.tyrell-rollbacks/20260917-082717-2c5ca2a674fe/Tyrell.app as the immediate canary rollback until normal release-retention policy expires it.
• If a documentation fact is found incorrect, append a corrective ticket comment and create a superseding changelog. Do not rewrite immutable gate evidence.
• If a future product finding requires another canary, it must start with fresh preflight and clocks; no R4 elapsed time may be repurposed.

Outstanding work

• No R5 is required: the owner decision accepted the six-hour result and superseded the further laptop soak for Build 26.
• Build 26 is exact and healthy on all six hosts; release monitoring for this build can stop.
• ISSUE-20260917-01 is resolved. Continue the distinct pre-existing allocator/inventory investigation only under ISSUE-20260912-01.
• No local AGY work is eligible for resumption.