rdmpw3275m post-reboot Tailscale and tyrelld recovery

Restored this host's existing Tailscale session after an orderly reboot and verified that the unchanged signed Tyrell rollback daemon and canonical hub both recovered without a new Tyrell incident.

Scope

• Changed host: rdmpw3275m
• Read-only verification host: rdmsm4x
• Project/runtime: Tyrell and fleet coordination transport

Changes

• Ran tailscale up on rdmpw3275m after the reboot left the existing logged-in client in Stopped state with Self.Online=false.
• Did not replace Tyrell.app, tyrelld, a LaunchAgent plist, source code, Git refs, or user data.
• Terminated only two sync processes started by this Codex task after they remained blocked against the temporarily unavailable hub.

Evidence

• last reboot reports an orderly local shutdown at 2026-09-11 15:14 EDT and reboot at 15:17 EDT.
• Local Tailscale returned to BackendState=Running, Self.Online=true; direct Tailscale ping to rdmsm4x then succeeded in about 1 ms.
• A subsequent agent_msg.zsh sync succeeded to all five peers.
• Local launchd started tyrelld PID 1820 at 15:18:35 EDT, runs=1, last exit=(never exited).
• The managed symlink still resolves to /Users/richh/Library/Application Support/Tyrell/releases/daemon-dbc440bd54b8/tyrelld with SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0, Team ZU2882L4HT, and Hardened Runtime.
• Both local data/status planes on ports 43117 and 43118 returned HTTP 200 for / and /api/status after startup inventory completed.
• Startup load was bounded: sampled top instantaneous CPU fell to 0%, the same PID remained alive, descriptor count was 40, and physical footprint was 806 MB with a 1,123 MB peak. There is no new tyrelld devmon incident directory after 14:00 EDT, so this reboot is not classified as a sixth high-RSS restart.
• Canonical rdmsm4x also recovered its exact same rollback hash, both 43117 and 43118 returned HTTP 200 for /api/status, and canonical source remained clean at main 53c0d8c17a4858fda4c182678e0baa823e603f77 with review ref 9a0fe66f8fb7a3d8251d3340efc6467255bb7265 unchanged.

Commands run

• tailscale status --json
• tailscale up
• tailscale ping --timeout=3s --c=2 100.87.66.12
• agent_msg.zsh sync
• last reboot, uptime, ps, top, sample, footprint, lsof, launchctl print
• curl probes against ports 43117 and 43118
• Read-only SSH verification on rdmsm4x

Backup and rollback

• No file backup was needed because no configuration or executable changed.
• If this runtime restoration must be undone intentionally, tailscale down returns the host to the prior stopped transport state; that would again interrupt canonical ticket/mail access and is not recommended during active monitoring.

Outstanding owner actions

• Exact Build 18 review head 9a0fe66f8fb7a3d8251d3340efc6467255bb7265 still needs explicit canonical-owner acceptance, signed/notarized universal artifacts, and the complete rollback-protected rdmbair15m5 canary before any newer production Tyrell launch.
• Local agy parents remain complete or handoff-pending and are not eligible for duplicate resumes; canonical accept/reject/integration receipts remain outstanding.