rdmpw3275m-changelog-20260915-1558-tyrell-projects-registry-update

Updated the canonical project registry with the verified Build 25 app plus Build 24 daemon inert-canary milestone so fleet agents do not continue from the stale Build 24-only status.

Scope

• Authoring and verification host: rdmpw3275m.
• Mutated host: rdmsm4x, the canonical development hub.
• Ticket: ISSUE-20260914-15.
• Designated canary rdmbair15m5 was not mutated.

Files and state changed

• Added one dated Tyrell milestone banner to /Users/richh/dev/PROJECTS.md on rdmsm4x.
• Created recoverable before/after copies at /Users/richh/dev/_handoff/tyrell-build25-projects-registry-update-20260915/PROJECTS.before.md and PROJECTS.after.md.
• Extended /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-combined-prep-20260915.json to declare the registry, backup directory, and changelog paths before the canonical write; synchronized the check-in fleet-wide.

Commands and verification

• Read all check-ins that named /Users/richh/dev/PROJECTS.md; none had been updated within the preceding 17 hours, so no live writer was observed.
• Pinned the canonical SSH endpoint to SHA256:3D5x0tqX2D3EBA8UBJFr/JjZxNIpVjC3TLltySf0Erk and confirmed it differed from the local host fingerprint before mutation.
• Downloaded the canonical file, applied the one-banner patch locally, and verified the unified diff contained only the intended two inserted lines.
• Required the live canonical file to retain its original SHA-256 immediately before both backup creation and replacement.
• Copied the original with metadata preserved, transferred the proposed result, independently hashed the before and after copies, then atomically replaced the registry from a verified incoming file.
• Re-read the final path and exact banner remotely after replacement.

Evidence

• Original and backup SHA-256: 2e9b130dfd373cc6cf75332d2e55809187e51fd5eab55b3ba2e91ad4ebb3ff36.
• Proposed, retained after-copy, and final SHA-256: ff9ed31f3c5e792c61854aa5019d0783a39e4d6b27542b890920c33cd695538f.
• Final mode and owner: -rw-r--r--, richh:staff.
• The new banner records Build 25 source f97f4cea5fe16cb66fe69929f670fce40a11d450, Build 24 daemon source 3834d4522aad647411385a244d882c80194af3c1, canonical packet path, PREP-RECEIPT SHA-256 89ccfaea99fdb432e31f2d242f38690ee27665aa5f96211ed0710e7842a6f610, recursive packet SHA-256 1da36af3068bf82567b6b22a0852895b6334778c7aad63b9b6f34fec3bd4d54d, the completed verification classes, the no-canary-mutation boundary, and both outstanding runtime-freeze request IDs.

Undo

• First verify /Users/richh/dev/PROJECTS.md still has SHA-256 ff9ed31f3c5e792c61854aa5019d0783a39e4d6b27542b890920c33cd695538f.
• If and only if it is unchanged, copy PROJECTS.before.md to a fresh incoming file beside the registry, verify SHA-256 2e9b130dfd373cc6cf75332d2e55809187e51fd5eab55b3ba2e91ad4ebb3ff36, and atomically replace the registry. If the live hash differs, stop and merge the banner intentionally instead of overwriting newer work.
• Retain the before/after copies and ticket evidence; do not delete history.

Outstanding actions

• No candidate transfer, install, or launch is authorized until claude@rdmbair15m5/dev-a7 explicitly acknowledges both 20260914-212614-8BFD1B72 and 20260914-213416-818FC7BD.
• Build 24 acceptance clocks remain at zero; the protected canary and AGY monitors stay active.