rdmpw3275m-changelog-20260914-1455-tyrell-build21-remediation-dispatch
rdmpw3275m changelog — Tyrell Build 21 remediation dispatch
The rejected Build 20 canary was left safely rolled back, the existing canonical Tyrell task was actively resumed for a distinct Build 21-or-later allocator fix, and the recurring monitor was retargeted to follow that work and the unchanged local AGY receipt lane.
Scope and exact changes
- No Tyrell source, installed app, daemon, database, or canary process changed in this addendum.
- Existing canonical Codex task
01a08a70-7b42-7ed1-aa30-1e3408453d0aonrdmsm4xreceived the bounded R11 evidence and Build 21-or-later source/review/test/sign/notarize request. The first two wait snapshots showed a new active turn started at epoch1789411933; no assistant message, tool marker, source receipt, or artifact receipt existed yet. ISSUE-20260912-01received an append-only dispatch-state comment. Build 20 remains prohibited.- Heartbeat automation
/Users/richh/.codex/automations/finish-tyrell-build-16/automation.tomlwas updated through the Codex automation API, remainsACTIVEevery 15 minutes, and is now namedFinish Tyrell Build21 canary + local agy work; SHA-256ecd6f3f7d43dd95ca4a6769c86e0d45452c0a7fb4e210e9a36ff0826cf45a9f5. - Coordination check-in
/Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrelld-build18-recovery-20260910.jsonnow records the canonical execution thread asactive_dispatch_only_no_source_receipt; SHA-256640ebf2ac81104728c26bcb72bd2aec35decdfada779f93ea4cc671c520f09b5, byte-identical onrdmsm4xafter the canonical fleet check-in sync. - Final R11 closeout evidence remains byte-identical locally and
canonically with complete manifest SHA-256
0eeae8ca9627eabfaa14c9f1f4141fd96b1db2d1e444bd1e24406eeed89c1dcd; content-onlyrsync -naci --omit-dir-times --delete-afterproduced no output. - Shared
PROJECTS.mdremains byte-identical locally and onrdmsm4xat SHA-2567042388fec4334e552134f45edc757fe68cac49e36e3b7fbaf6c0f8df649f8a6. - Fresh canary read at 14:50:24 EDT kept the exact healthy rollback:
Build 15 daemon PID
94015, SHA-256dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0, one run/never exited; Build 17 app executable SHA-2568693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e; both status APIs HTTP 200 valid JSON; database quick_checkok, one additive column,153533rows; one app and bar; recovery unloaded with plist and active marker absent. - Local AGY authoritative files remained unchanged at manifest SHA-256
7117f14cd805e77270cf60b8fc36be5746e33284e4e6245f82ae446d92970401and STATUS SHA-256bfb8601ed8d976b46ce4237f545adcbdb1f9c5e71ad39e30aff91ef49b35d99f; exactagyCLI count was zero and exact Antigravity main-process count one. There was no real provider quota/reset event or eligible unfinished parent, so nothing was relaunched.
Commands and verification
Codex list_threads/read_thread/send_message_to_thread/wait_threads for canonical task 01a08a70-7b42-7ed1-aa30-1e3408453d0a
Codex automation_update for finish-tyrell-build-16
ticket comment ISSUE-20260912-01 <dispatch state>
ticket heartbeat TASK-20260911-01, ISSUE-20260912-01, ISSUE-20260914-10
ssh [email protected] <launchctl, libproc, shasum, codesign, curl, sqlite3, process-count verification>
ssh [email protected] /Users/richh/dev/fleet/maintenance/scripts/fleet_checkin_sync.zsh
rsync -naci --omit-dir-times --delete-after <R11 evidence>/ <canonical evidence>/
shasum -a 256 <automation, check-in, evidence, and PROJECTS.md>
Undo and outstanding work
- Do not undo by relaunching Build 20. Keep exact Build 15 daemon plus Build 17 app until a separately identified candidate passes every gate.
- The recurring monitor is deliberately retained. Pause/delete it only if Rich supersedes the goal or after a newer build has full acceptance and all local AGY handoffs have explicit canonical receipts.
- The canonical task must first return explicit ownership and source evidence; active dispatch is not acceptance. A future artifact must be independently reviewed, fully tested, signed/notarized, and canaried from zero before installation beyond the designated canary.
- The canary Markdown changelog is present on
rdmbair15m5; Apple Notes request20260914-144418-56B0DF3Bremains pending an explicit Aqua-session reply.