The CLI automatically deletes selected stale files and caches on a schedule, which presents a data-loss risk without a direct cleanup request. Its cleanup purpose and safeguards are documented, so this warrants a warning rather than a block.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Starting a `wb` command; the cleanup runs on a schedule, daily locally or hourly on CI.
Impact
Stale temporary files, worktrees, build caches or CI workspaces may be deleted when users expected to retain them.
Mechanism
A detached local process or synchronous CI cleanup checks age and repository state, then recursively removes selected stale paths and prunes mise caches.
Evidence
dist/index.jsdist/gc-tj8rtIiF.jsREADME.md$GHQ_ROOT (default ~/ghq): stale .tmp entries, linked worktrees, node_modules and directories marked by CACHEDIR.TAGSibling CI job workspaces under the runner work directory~/.cache/wb/gc.logmise-managed caches