rdmpw3275m-changelog-20260914-1715-tyrell-build23-r1-canary-launch

Build 23 R1 was independently validated, installed only on the designated rdmbair15m5 canary, and launched under the unchanged fail-closed memory guard; it is soaking and is not accepted for rollout.

Scope

• Coordinator/control host: rdmpw3275m.
• Canonical source/signing host: rdmsm4x.
• Only runtime-mutated host: designated canary rdmbair15m5.
• No fleet expansion, main-branch integration, public release, or Build 22 daemon deployment occurred.

Why this changed

• The original tyrelld outage was traced to a LaunchAgent that referenced a mutable .build/release/tyrelld path missing after reboot. Stable hash-addressed deployment remains the recovery model.
• Builds 20 and 21 failed the unchanged short physical-footprint growth gate and remain prohibited.
• Build 23 source commit 093d653493be92aed0fb39779f52d5eaef04230b fixes a proven activity-event queue leak while retaining genuinely pending direct events. It does not claim that allocator fragmentation was fully explained.

Files and state changed

• Installed Build 23 app only on rdmbair15m5; exact executable SHA-256 631d3a60eb57623d4a6afecba2e2085f8a8b2c132fac2c0f3803765566d5c732.
• Installed/started hash-addressed Build 23 daemon only on rdmbair15m5: /Users/richh/Library/Application Support/Tyrell/releases/daemon-6afb7431fb42/tyrelld, SHA-256 6afb7431fb4288875b6ba4ad591bce8a27156ebb3176546a4ac42ca5b6cd791c.
• Active canary stage: /Users/richh/.tyrell/build23-canary-r1-20260914-093d653.
• Fresh consistent DB backup: /Users/richh/Library/Application Support/Tyrell/backups/20260914-1656-build23-r1-preflight-093d653/tyrell.db, SHA-256 94cd2cf7b743f54a75235d49e6ff3d8095866a4a179252c906fb1fce40d6833d.
• Retained rollback app: /Applications/.tyrell-rollbacks/20260914-170023-2c5ca2a674fe/Tyrell.app.
• Local immutable launch packet: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build23-r1-launch-20260914-1701.
• Canonical immutable launch packet: /Users/richh/dev/_handoff/tyrell-build23-memory-20260914/canary-r1-launch-20260914-1701.
• Canonical launch tooling and project-index receipts: /Users/richh/dev/_handoff/tyrell-build23-r1-launch-20260914.
• Updated /Users/richh/dev/PROJECTS.md Tyrell row only; after SHA-256 ddf2ed9eb672b5727debeb2a1b383d453c09e9ef52e8a0b307345d1b19ecc5ce.
• Updated and fleet-synchronized /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrelld-build18-recovery-20260910.json, SHA-256 15350cc2930f03c44113f1e104963ac70c3669c6419bea8df33eaf588c7edb00.
• Added a reproducible launch milestone to ISSUE-20260912-01 and relayed diagnostic allocation evidence in bus message 20260914-171149-5748CF68.

Commands and verification

• Compared all 91 producer-manifest entries and independently verified the source, review, tests, signatures, notarization receipts, artifact hashes, architectures, and frozen handoff.
• Ran fresh app-install dry run and install, nonce-bound app probes, canary-receipt checks, database backup and quick_check, rollback preflight, dependency preflight, nine guard/interlock tests, launchd-disable interlock, strict codesign, Gatekeeper, and exact hash checks.
• Launched the candidate through the power-protected guard and re-ran /Users/richh/.tyrell/build23-canary-r1-20260914-093d653/verify_guard_power_protected.zsh.
• Seven frozen one-minute samples span 360.052417 seconds with one PID/start/path, max gap 60.041160 seconds, descriptors 26..31, TCP exactly 2, all status and permission probes HTTP 200 valid JSON, and AC/open-lid throughout. Physical footprint was 261702904 -> 305120648 bytes with startup maximum 407012792 bytes; this is early health evidence only.
• The diagnostic allocation sidecar produced four successful footprint -f bytes and vmmap -summary snapshots; no inventory pass had completed at capture.
• Verified all 72 entries in the launch packet manifest, RC 0. MANIFEST.sha256 SHA-256 is edeb89813d18739c10b34a3bea83eb7c4178d8728bf1b444a0482d001ab09867; local-to-canonical rsync --dry-run --delete was empty.
• Ran the canonical fleet check-in sync and verified the same check-in SHA on rdmpw3275m, rdmsm4x, and rdmbair15m5.

Rollback

• The fail-closed guard retains exact signed Build 15 daemon SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0 and Build 17 app SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e.
• If any unchanged gate fails, preserve the complete stage first, verify the automatic rollback exactly, and do not relaunch before a distinct reviewed successor exists.
• The DB backup above is retained for recovery, but no database restore is currently warranted.

Outstanding actions

• Keep rdmbair15m5 on AC with the lid open; do not reboot or sleep it during the active candidate proof.
• Short gate cannot be evaluated before 2026-09-14 17:41:47 EDT; six-hour gate before 23:11:47 EDT; fixed 24-hour gate before 2026-09-15 17:01:47 EDT.
• Repeated unchanged inventory, CPU, fresh-app, controlled reboot, integration, and rollout gates remain open.
• Build 22 stays READY_QUEUED_NOT_INSTALLED; never deploy its daemon.
• AGY monitoring continues separately; no genuine unfinished eligible parent or real provider quota-reset evidence currently authorizes a launch.