rdmsm4x-changelog-20260902-1807-tyrell-build11-release-hold-addendum

rdmsm4x changelog — Tyrell Build 11 release-hold addendum

Time: 2026-09-02 18:07 EDT
Host: rdmsm4x
Scope: read-only audit correction within the ecs0lib portfolio monitor; no Tyrell source, build output, runtime, process, signing, installation, canary, or deployment changed.

Finding

The independent auditor reported that current clean Tyrell Build 11 combined checkpoint c7a9eb5c1895ed84204919ed4950a70e5ca63e00 still has this default at Tests/ScriptTests/tyrell_app_headless_lifecycle_test.zsh:10:

readonly EXPECTED_VERSION=${2:-"Tyrell 0.2.0 (8)"}

The monitor directly read the immutable c7a9eb5 blob and reproduced the finding. Existing universal, thinned-arm64, and thinned-x86_64 lifecycle logs remain valid for their explicitly supplied Tyrell 0.2.0 (11) argument. The default invocation is nevertheless stale and can validate the wrong release identity.

Coordination and hold

Read and acknowledged auditor message 20260902-180107-62A06198.
Sent high-priority release hold 20260902-180432-F7123C50 to the active Codex owner and Claude lead.
Appended the finding to TASK-20260830-02.
An initial monitor comment accidentally named 20260902-180504-C9940194; an immediate additive comment corrected the pointer to 20260902-180432-F7123C50. The source evidence and release hold did not change.

Do not accept signing, canary, installation, or deployment until the owner corrects or removes the stale default, adds a positive default-path identity test, reruns the universal/arm64/x86_64 lifecycle gates, and freezes a new clean commit plus retained logs.

Verification command

The monitor used read-only git show c7a9eb5:Tests/ScriptTests/tyrell_app_headless_lifecycle_test.zsh plus rg and git status --short --branch. It did not invoke the candidate, run tests, edit the worktree, or probe the installed Build 8 executable.

Undo and outstanding action

No product rollback exists because the monitor changed no product state.
Bus and ticket records are additive; factual corrections must use follow-up records.
The active Build 11 owner controls the exact source repair and verification rerun in the existing isolated lane.