Repository navigation
v0.14.0
Two gaps this repo had already written down and left open: a wall-clock budget
that silently did not apply on macOS, and a bash-3.2 compatibility claim that
lived only in a code comment. Test suite 468 → 477 assertions (counted by
summing bash tests/run-all.sh, at the previous release commit and at this one).
The 0.13.0 entry's "456" is not wrong so much as early: tests/test-packaging.sh
landed later in that same cycle carrying exactly the missing 12, so a fresh count
of the v0.13.0 tree is 468. Both numbers here were measured, not carried forward.
Behavior change, macOS only — read this if you schedule /polish.
unattended-polish.sh probed only timeout, so on a mac with Homebrew
coreutils — where GNU coreutils installs the binary as gtimeout — a scheduled
polish ran with no wall-clock cap, while the autoloop driver and the
stop-gate, both of which fall back to gtimeout, stayed bounded. The probe is
now timeout → gtimeout, so on such a host a nightly polish is from now on
killed at LOOP_ENG_MAX_MINUTES (default 120 minutes) where it previously
ran to completion. To keep long runs: raise LOOP_ENG_MAX_MINUTES (0 is
refused and falls back to 120 — timeout 0m means "no limit", which is the
opposite of what a budget knob's lowest value should do), or pin 0.13.0. A host
with neither binary still runs uncapped, but now says so on stderr, where the
scheduler's own log keeps it, instead of dropping the budget in silence. Linux
is unaffected: timeout was always found there.
One known consequence of the cap being live on macOS, surfaced by the pre-ship
review and deliberately left as-is: a polish run the cap kills exits 124, and if
its partial log happens to carry a provider-limit word (quota, overloaded),
this runner's rate-limit branch reports EX_TEMPFAIL 75 — "try again later" —
rather than a timeout. The autoloop driver distinguishes 124 explicitly; this one
does not yet. Pre-existing logic with a bounded false-positive surface (the grep
runs only on failed runs), newly reachable here, and a fix would be its own
change rather than a line in a release.
update-notify.sh joins the bash-3.2 CI leg. It is a SessionStart hook, so
on a stock macOS box it is bash 3.2 that runs it in every real session — and the
only thing asserting it could was a comment in its own header, while README said
outright that the test-bash32 job did not cover it. That job now runs six
suites and syntax-checks six scripts. Verified under a real 3.2.57 before
wiring, via CLAUDE.md's docker recipe (extended to the same six suites): all six
green, test-update-notify 26 passed / 0 failed, and the six-script bash -n
list parses. musl is not BSD, so the macOS cell is the one the CI leg adds.
tests/test-update-notify.sh also stops resolving bash from PATH when it runs
the hook and uses $BASH, the interpreter running the suite: under the 3.2 leg a
5.x homebrew bash that happened to be installed would otherwise have run the
hook, and the leg would have reported a 3.2 verdict it never tested.
Evidence for the polish fix, in the order it happened:
tests/test-unattended-polish.sh 30 → 39 assertions. Run against the pre-fix
driver, exactly the arms carrying the fix fail and everything else passes —
35 passed / 2 failed for the gtimeout arm and the stderr-warning arm, and later
38 / 1 for the rolling-log assertion the pre-ship review added. Post-fix: 39 / 0.
The both-installed arm passed throughout, which is what proves the harness rather
than the fix. Both absent-binary arms run the driver under a minimal bin dir of
symlinks to exactly what it and the stub exec, because no real PATH can be made
to lack timeout on demand; each prerequisite symlink is asserted, so a missing
one cannot masquerade as a driver bug.
Docs: the README Requirements table drops its "Known, not yet fixed" admission,
and its intro names the guard-weakening rows correctly — rows 1-4, not "1-3 and
5", which counted curl (a missing notice, not a guard) and skipped the polish
timeout row.
Live-install smoke (RELEASING.md §1, against this release's content): PASS on
Claude Code 2.1.278, via a genuine claude plugin marketplace add sdsrss/loop_eng
claude plugin installinto an isolatedCLAUDE_CONFIG_DIR. A GitHub source,
so the copy that enforced is the version-pinned
plugins/cache/loop-eng/loop-eng/0.14.0/one and not the marketplace clone —
both existed, andarm-contractprintedarmed fromthat cache path. No
source-type disclosure is owed this time: 0.14.0 was onmainbefore the smoke
ran, which is what makesmarketplace add owner/repoinstall the release's own
content.
Machine-verified rather than model-reported, by instrumenting the live cached
hooks. Step 4: DENY-FIRED … root=<the real cache path> — not the
<loop-eng plugin root> placeholder, so CLAUDE_PLUGIN_ROOT reaches hook
processes — and .loop/evidence/smoke.log did not land under
--permission-mode bypassPermissions. Step 5: BLOCK-exit n=0..2 then
CEILING-RELEASE count=3 over a generated_by: run-contract.sh ledger reading
all_green: false with the red criterion false, while .loop/evidence/red.log
was written by the runner — the same directory the model had been denied a moment
earlier, which is the whole invariant in two steps. Step 6: a full
/loop-eng:autoloop round reached all_green: true on both criteria, hello.txt
held hi, and .loop/active + .loop/criteria.sha256 were removed by the gate
rather than by the model. Reachable only if ${CLAUDE_PLUGIN_ROOT} expanded
inside the command markdown. That session's own closing summary asserted
.loop/active was "still armed"; the disk said it was gone. The disk is the
authority here, which is the point of the plugin.
Pre-ship review (independent reviewer, fresh context, over dcf2745..9b9f62f):
every numeric claim above re-measured, including under a real 3.2.57; no blocking
finding; six accepted repairs. Two were load-bearing. The new UNBOUNDED warning
went to stderr only, and this script's own cron example ends >/dev/null 2>&1 —
so the warning was discarded by the very invocation it is written for, leaving a
plain exit=0 in .loop/unattended.log for an uncapped run, and making the
"where the scheduler's log keeps it" line above false for anything but the systemd
path. It is now tee'd into the rolling log, like the dirty-tree refusal. And the
test-bash32 leg's "Prove /bin/bash is stock 3.2" step printed the version
without asserting it: a runner image that ever ships a newer /bin/bash would
have kept that leg green while testing the wrong interpreter — the same
silent-disarm shape this release's other half exists to close. It now fails the
job unless BASH_VERSINFO[0] is 3. Four smaller ones: README's "each says so"
now excludes arm-contract.sh's advisory red-check (which really does just run
unbounded), the env-var table stops crediting timeout alone for the budget, the
both-installed arm asserts that exactly one wrapper ran rather than trusting a
substring on an append-only record, and the minimal-bin-dir comment names
/usr/bin/env as the one prerequisite no symlink can cover.