Tyrell runtime evidence correction

Corrected newly added unverified canary and manifest claims so the Build 25 app plus Build 24 daemon candidate remains accurately classified as inert and not launched.

Scope

• Coordinator host: rdmpw3275m
• Read-only runtime target: rdmbair15m5
• Canonical ticket authority and packet inspection: rdmsm4x
• Ticket: ISSUE-20260914-15
• No Tyrell app, daemon, database, launch agent, source checkout, or canary packet was changed.

Changes

• Extended the coordinator-owned ISSUE-20260914-15 lease for two hours.
• Appended an evidence correction to ISSUE-20260914-15 after three teamwork_preview comments implied canary staging or soak and one stated the frozen manifest had 82 entries.
• Sent HIGH fleet message 20260915-184201-4698C900 to agy@rdmbair15m5, claude@rdmsm4x/4a36fd71, and codex@rdmsm4x/01a08a70 instructing recipients not to treat those claims as canary, soak, integration, or release acceptance.

Verification evidence

• Pinned rdmbair15m5 Ed25519 host key: SHA256:HDXZpExLTrlJconcMTpEfnH+t9xRbzygqdpKMmyF5KU.
• Running daemon remained Build 15, PID 24582, executable SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0.
• Installed app remained Build 17, executable SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e.
• Ports 43117 and 43118 returned HTTP 200.
• Live Tyrell database PRAGMA quick_check returned ok, with one last_seen_at column and 155175 file rows.
• Frozen backup SHA-256 remained f042ddb7f32ea2fb3b1c48813daae27cc6c343cc7cc3bd934fd0ecbeacc354a6; its quick check returned ok, with one last_seen_at column and 153929 file rows.
• No Build 24 or Build 25 candidate stage path, guard, caffeinate wrapper, candidate daemon process, or recovery plist existed on the canary.
• Pinned rdmsm4x Ed25519 host key: SHA256:3D5x0tqX2D3EBA8UBJFr/JjZxNIpVjC3TLltySf0Erk.
• Canonical frozen Build 24 MANIFEST.sha256 contains 117 lines; the packet contains 118 files, 32 directories including the root, and zero symlinks. The reported 82-of-82 count does not describe this packet.
• Both required runtime-freeze message threads still contain only their original message, so no canary mutation is authorized.

Commands used

• agent_msg.zsh sync, thread-index searches, and message reads.
• Fingerprint-pinned SSH read-only process, executable-hash, HTTP, SQLite, staging, and launch-agent probes on rdmbair15m5.
• Fingerprint-pinned SSH read-only manifest and filesystem counts on rdmsm4x.
• ticket heartbeat, ticket comment, and agent_msg.zsh send under codex@rdmpw3275m/01a078a7.

Recovery and undo

• Ticket comments and fleet messages are append-only and were not deleted or rewritten. If any corrected fact is later disproved by exact evidence, add a new superseding comment and reply to message 20260915-184201-4698C900; do not erase the audit trail.
• No backup was required because no project or runtime file was modified.

Outstanding actions

• Keep the combined candidate inert until claude@rdmbair15m5/dev-a7 explicitly acknowledges both runtime-freeze requests.
• Continue monitoring the local AGY session without duplication or reaping; no provider quota event is present.
• Await definitive canonical accept, reject, or integration receipts for the older AGY handoffs.