Repository navigation
v1.5.3
1.5.3 — 2026-10-17
Operator-command hardening: setup --remove, concurrent runs, --host and
--dry-run now do what the operator asked, refuse what they cannot do and
say so. A second pass with the ECC Python, silent-failure, security and
test-coverage reviewers closed the gaps the first pass left (listed after the
first-pass items). No release pin moved since 1.5.2, so no card was due for a
recheck.
setup --removeno longer deletes a binary that another host still
launches. Every host gets a row; one whose CLI is not run (not on PATH, or
left out with--host) has its user-scope file read, and while it still
registers the app at the managed binary, or cannot be read, the binary, pin
and evidence stay. Before,--remove --host claudedeleted the binary under
a live Codex registration, and a host CLI missing from PATH left its
~/.claude.jsonorconfig.tomlentry pointing at a deleted file, both
reportedok.- A failing
mcp removeis reported in that host's row and the run continues
with the other hosts and apps; before, it aborted the whole removal without
a report after earlier hosts were already unregistered. A failed binary
delete or pin rewrite is reported the same way. - The pin now stays while any registration that may still launch the managed
path is kept (for example one whosemcp gettimed out), so a later
--removecan still prove that entry is Storytold's and remove it. Before,
the pin was dropped and that registration could never be removed by
Storytold. - One changing run at a time:
setupandsetup --removehold an OS advisory
lock (setup.lockin the state directory) for the whole run, released by
the OS when the process ends. The<lock>.writingmarker guarded only the
lock rewrite, so two runs could clear each other's staging or recovery
marker. - An app without root flags and no
--acknowledge-unconfinedis skipped
whatever its install path holds; an outdated pin or a foreign file there no
longer stops the rest of the batch. The message names what the next run
would meet. - A host named with
--hostwhose CLI is not on PATH now fails the run
(other named hosts are still registered); before, it was a warning with
exit status 0. --dry-runshares the real run's decision function and reports, per app,
binary(keep,install,upgrade,skip,refusewithreason), a
downloadonly where one is needed, per-hostregistrationsjudged from
the user-scope files,predicted_statusand an overallwould_pass.
Before, it listed a download and a registration for every app, including
ones the real run would skip or refuse. A work root that exists but is not a
Storytold workspace is now refused before any directory is created.- Tests: nine new regression tests; the test runner strips
CLAUDE_CONFIG_DIRandCODEX_HOME, and the CLI tests point
CLAUDE_CONFIG_DIRat a temporary directory, so no test reads the
operator's real host settings.
Second pass (ECC review of the first):
setup --removekeeps the binary and pin under a kept registration whose
command the host CLI does not show (claude mcp gettext without a
Command:line, unparseablecodex mcp get --json), and under one a local
or project entry shadows inmcp getwhile the user-scope file still names
the binary. Before deleting, it now searches both hosts' files for any
registration that starts the binary: another server name, another spelling
or symlink of the path, or a Claude Code local-scope entry, listed in
referencesby host, scope and name only. Anmcp removethat exits 0 is
trusted only once the user-scope file no longer lists the entry.- A registration carrying settings
mcp addnever writes (tool lists,
timeouts, a non-stdio type) is no longer treated as Storytold's: removal
keeps it, and--replacerefuses it instead of losing those settings on a
failed add. - A failing evidence archive, or any unexpected error in one app, no longer
endssetup --removewithout a report: it becomes that app's row and the
other apps still run. A realsetupthat stops at a failure lists the apps
it never attempted asnot_reached. - Refused before anything is created or downloaded: a leftover
<lock>.writingmarker (also by--remove, before any binary is deleted),
a state or evidence directory that is not owner-only, and a bin directory
that group or others can write, which used to be found only after a
candidate was promoted and pinned. --dry-runpredicts those refusals, the Linux/Windows provenance gate (no
bundle or no cosign without--trust-upstream-sums), a--replacethat
could not restore the old entry, and an unreadable user-scope file
(registration_unknown); it exits 1 whenwould_passis false, like
--remove --dry-run. A realsetupreport without a recognized status no
longer reads as success.- Host files never reach a report: unparseable or too deeply nested JSON or
TOML (aRecursionErrorused to escape as a traceback) gives a fixed
message instead of the parser's text, which could quote keys, and only text
commands of at most 300 characters are shown.doctordoes the same. - The run lock refuses a lock file that is a symlink, reparse point or not a
regular file (Windows has noO_NOFOLLOW), names a filesystem without file
locks instead of reporting "another setup run", always closes its file on
Windows, and two first runs racing to create the state directory meet the
lock instead of a rawFileExistsError. - Docs: operations says that
claude mcp get, used by--remove, its dry
run,--listand registration, starts the registered server for its health
check, as a Claude Code session does. - Tests: thirteen more, 260 in all, including a run lock held by another
process blockingsetupand--remove, the Windowsmsvcrtbranch through
a fake module, everyunrun_hostbranch, failed deletes and pin rewrites,
recovery markers in a dry run and a Linux provenance preview; the
killed-holder test has a watchdog and waits briefly for Windows to release
the lock.