Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260902-2051-tyrell-build15-evidence-api

Added a source-only Tyrell Build 15 evidence API candidate so fleet freshness, usage authority/advice, and daemon identity can be displayed without inventing missing data.

Tyrell Build 15 evidence API — rdmsm4x changelog

Date: 2026-09-02 20:51 EDT
Host: rdmsm4x
Scope: source-only isolated worktree; no live runtime or fleet mutation

What changed

Exact repository state

Files touched are the 23 paths recorded by the exact base-to-HEAD diff in the handoff: Package.swift, INTERFACES.md, SESSION-STATE.md, ISSUES.md, the bounded TyrellCore/daemon/MCP/menu-bar/app/dashboard source files, and their values-free tests. The canonical Tyrell checkout and ecs0lib were not edited or cleaned.

Commands and verification

Logs and their SHA-256 values are recorded in the handoff. The full-test log is /Users/richh/dev/_handoff/tyrell-build15-evidence-api-20260902-logs/full-swift-test.log with SHA-256 6864eeb6ebcf60fa42d6cb90b6557e6e6f30a4003b2acc84104ceefd7e3d029e.

Preservation, rollback, and outstanding owner actions

No user data was overwritten, so no data backup was required. The isolated worktree, two Git commits, values-free logs, and handoff are the recovery artifacts. No app, daemon, launchd service, database, CloudKit container, credential, signing identity, canary, or deployment target changed.

To undo after integration, revert bb7a361c00257d4b7d72d4e0087e48b6b1b74659 first and 70fd479279ce28f15aacfb30fb733909c6294bbe second, then rerun the same full and release gates. Before integration, retain the evidence and simply reject/remove only the isolated candidate lane.

Owner action remains: review and integrate onto the selected Build 15 successor, rerun exact-source gates, sign on rdmsm4x, validate first on the designated rdmbair15m5 canary with direct typed API observation, then make any fleet rollout a separate accepted state. The live fleet remains Build 11.