replume-cli 0.2.4 → 0.2.5

package/README.md

@@ -26,6 +26,8 @@ replume init
 
 Start your agent in that folder. That is the whole setup. `replume init` installs the hooks and writes `.replume/config` with `mode: auto`. The first thing you ask the agent is the task. You do not write a contract or confirm it. If the project has no commit yet, make one first (`git add -A && git commit -m "initial"`): Replume compares the agent's work against it, and `replume init` reminds you when there is none.
 
+Optional before the first task: `replume init --check` tries a base test in an isolated copy with a 55-second limit. It says whether a test was already red or the runner could not start. It skips dependency-install steps, warns about `npm ci --offline` and its separate cache, and does not record or change the task baseline. Use `--isolation worktree` or `--isolation docker` to select the check mode.
+
 `replume init --approve` writes `mode: approve` and keeps the older path: `replume draft --task`, review, `replume confirm`, then `replume accept` after verify.
 
 Scenarios are optional. Without one, verify can PASS when all of these hold: the contract's `test_command` runs at least one test and passes; nothing is FAILED, EXTRA or TAMPERING; and the ledger has an agent session for the task with an event naming each changed file. Otherwise the file is `NOT CHECKED` and the verdict is `INCOMPLETE`, with the reason: "agent steps not observed" (no session for this task in the ledger) or "change not seen by hooks" (no event names the file). A manual edit made without hooks therefore gives `INCOMPLETE`. Scenarios listed in `must_check` are required.
@@ -125,7 +127,7 @@ The container has no `node_modules`. When `package.json` declares dependencies a
 
 This stage **only** runs in Docker, even if scenario verification used the worktree fallback. For a detected web app, Replume uses the [official Playwright image](https://playwright.dev/docs/docker) pinned to `v1.64.0-noble`. On first use it announces the roughly 3.5 GB local image download and builds a local image with `playwright@1.64.0`, because the official image contains browsers but [not the npm package](https://playwright.dev/docs/docker). Image preparation contacts the image/npm registries; the app and browser run together over localhost in a fresh container with `--network none`, a read-only repo mount, and no host Docker socket. CLI and HTTP probes do not pull Playwright. Use `--runtime-image <local-image>` to supply another image; Replume never pulls a custom image. A Dockerfile `CMD` is run against the selected image and clean commit, without a Dockerfile build. If anything cannot run, the report says NOT CHECKED. An automatic end-of-task integration can call `runRuntimeAtTaskEnd` from `src/sandbox/index.ts`; its `enabled: false` option and CLI `--no-runtime` disable the stage. Existing projects should add `evidence/` to `.replume/.gitignore` before running this option; new `replume init` projects include it. Docker is useful isolation, not a perfect security boundary.
 
-Commands: `replume init`, `replume status` (what Replume does in this repo: mode, agent hooks, Docker, model review and what it sends, the last Stop check, last report), `replume uninstall`, `replume task`, `replume draft`, `replume confirm`, `replume confirm-config`, `replume watch`, `replume verify`, `replume accept`, `replume report`, `replume share`, `replume github`, `replume memory`, `replume usage`, `replume demo`, `replume judge-eval`, `replume doctor`, `replume install`, `replume hook`.
+Commands: `replume init`, `replume bug` (packs the last report, the redacted ledger and local facts into one file and prints where it is; sends nothing), `replume status` (what Replume does in this repo: what it will run, mode, agent hooks, Docker, model review and what it sends, the last Stop check, last report), `replume uninstall`, `replume task`, `replume draft`, `replume confirm`, `replume confirm-config`, `replume watch`, `replume verify`, `replume accept`, `replume report`, `replume share`, `replume github`, `replume memory`, `replume usage`, `replume demo`, `replume judge-eval`, `replume doctor`, `replume install`, `replume hook`.
 
 ### Local task metrics (first slice)