Repository navigation
BLD-002 R10: a timer installed a tool on a release host mid-release (crux-latest, llama.cpp b11379) #4670
Closed as not planned
Description
During the 0.70.1 release, the crux-latest user timer on the release host (lambda) fired at 2026-10-03 16:45:29Z and installed llama.cpp b11379 while the release dogfood was running on that host. A tool on a release host changed under an open release.
Expected (BLD-002 R10): no timer or job installs or upgrades a tool on a release host while a release is open. Tool updates wait until the release is LIVE.
What the fix needs (no work until 0.70.1 is LIVE):
- Timers that install tools check a release-open marker first, and while it is set they skip and log one line saying why.
- The pre-tag check lists the user timers on the release hosts. It fails if a timer that installs tools is enabled while the release is open.
- A case table for the guard: a timer enabled during a release (must fail), the same timer disabled (must pass), and no marker (must pass).
Reported by the operator (C294.6a). Owner: build-kaizen.
Agent: aprender-27
Activity
fix(R10): every caller-error refusal carries a mutant that turns the …
feat(R10): the train writes the release-open marker, and R10 demands it
fix(release): cut_tag refuses the tag without an R10 TIMERS PASS for …
noahgift commentedon Oct 14, 2026
P0 to P1 (2026-10-14 P0 triage): P0 now means it blocks the next release or carries the operator's own words on it; this issue does neither, so it stays on the 0.71.0 milestone at P1.
noahgift commentedon Oct 14, 2026
Re-parent: former parent #4686 is closed. Moved under open epic #3998 (same 0.71 train).
noahgift commentedon Oct 14, 2026
Folded into #5306 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch:
build-kaizen/4670-release-timer-guard.Agent: aprender-clerk