[2.24.2] — 2026-10-05
Fixed
monomind security defend no longer crashes when a threat is detected (#641). The per-severity colour was chosen by extracting output.error/warning/info/dim as bare function references, which dropped the this binding and made the first detected threat throw "Cannot read properties of undefined (reading 'color')". The formatter is now invoked on output.- Test-suite temp dirs no longer leak into
/tmp; a leaking test file now fails (#644). Tests that created temp directories outside the suite's managed temp root left litter in the real /tmp; the suite now keeps temp dirs under its own root and fails the file that leaks one.
- An org run's sandbox stubs no longer show up in
git status (#649). A role in a repo checkout holds empty stub files in the repo root for the whole run (.bashrc, .gitconfig, .claude/hooks, …); they read as debris and tripped "git status is clean" checks. While they exist the runtime now lists them in a marked block of the repo's info/exclude (linked worktrees included), recomputed from what exists on disk, and removes the block when they are gone, on release, on a signal or exit, and on reclaim after a SIGKILL. A real file of the same name with content is never named.
monomind security defend no longer crashes when a threat is detected (#641). The per-severity colour was picked by pulling output.error/warning/info/dim out as bare function references, which lost the this binding, so the first detected threat threw TypeError: Cannot read properties of undefined (reading 'color'). The formatter is now invoked on output.- The full-mode MCP tool count in the docs is derived from the registry, not typed (#642).
doc/concepts/mcp-server.md, opencode.md and antigravity.md said MONOMIND_MCP_FULL=1 advertises 219 tools; tools/list over stdio returns 198 (the default roster is 20). The two counts are now doc-count markers (mcp-tools-full, mcp-tools-default) that scripts/generate-doc-counts.mjs reads from the built CLI's registry, so --check fails when a doc states another number.
org sign from an org role now refuses plainly instead of appearing to write to the operator directory (#643). The operator-credential directory (~/.monomind/orgrt-operator) is hidden from every role sandbox on purpose, so a role never signs or reads the key. Where the sandbox mounts an empty tmpfs over it, org sign seemed to succeed and the signature vanished, so org run then failed. org sign now checks first and refuses before writing, saying the directory is protected from org roles and only the operator signs, and org run explains a missing signature the same way. Documented in doc/commands/org.md. The protection is unchanged.- The test run's teardown removes read-only temp directories (#650). A test that leaves a
chmod 0500 directory under its temp dir made the run's teardown fail with EACCES ("error during close"); it now makes the tree writable first.
npm: monomind@2.24.2, @monoes/monomindcli@2.24.2
