karotkriss cwcli lifecycle commands: init / rm / restore (sharp edges)
Each note guards a real shipped bug; keep the root-cause "why" so a later change does not silently
re-break the fix. The one-line contracts for these commands live in the always-loaded AGENTS.md
"Important Components" section; the deep incident detail is split by command into the reference
files below. Read only the one for the command you are touching.
| You are touching... | Read |
|---|---|
core/init.py / commands/init.py - version gating, secret env-transport, existing-bench reuse, container-start spinner race, the exec-stream exit-code honesty |
references/init.md |
core/rm.py / commands/rm.py - what deletion removes (including the project's own compose network), conf/-only archive, recache-under-spinner deadlock, the C1/H5/M11 data-safety gates, multi-bench per-bench backup, the stopped-project start -> back up -> delete flow |
references/rm.md |
core/restore.py / commands/restore.py - receive-mode + normal-path data-safety, selectors, secrets off argv, streamed copies, and the six restore+inspect bugs (shared utils/bench_sites.py site detection, default-site resolution, migrate+restart) |
references/restore.md |
commands/start.py, stop.py, status.py, restart.py, logs.py + core/supervision.py, start.py, stop.py, status.py, restart.py, logs.py - the supervisord per-process supervision substrate: PID-keyed idempotency (the pkill double-start bug), bench-scoped stop, config/launcher generation, per-process log files, the stdout-token-only status contract, single-program restart + auto-heal, the restore-restart tension |
references/start-status.md |
core/scale.py / commands/scale.py + axi scale - widen the published port range past six benches: read bench config as the port truth, the mandatory --no-deps DB-safe recreate, v13/v14 toolchain repair after recreation, and consent-as-a-core-decision |
references/scale.md |
rm is the most safety-critical command in the codebase: its backup gate fails closed and a
regression there can silently destroy data. Read references/rm.md in full before changing it, and
validate any change with the full-lifecycle dangerous-delete E2E required by the AGENTS.md
"Captain standards" (real init -> seed data -> rm-with-backup, against the worktree's editable
install). The restore/init credential and confirm flows are the canonical example of the
"support BOTH interactive and non-interactive modes" captain standard - see the auto_enter=False
note in references/restore.md and the cwcli-e2e-testing skill for the pty recipe.