@critiquedotsh/harness 0.1.7 → 0.1.8

package/README.md

@@ -7,7 +7,7 @@
 | **CritiqueCode** (this package) | [`@critiquedotsh/harness`](https://www.npmjs.com/package/@critiquedotsh/harness) | `critique-code` | Author: write the change, then survive review |
 | **Critique CLI** | [`@critiquedotsh/cli`](https://www.npmjs.com/package/@critiquedotsh/cli) | `critique` | Sidecar reviewer for agents you already run |
 
-Same npm org. Different products. Do not install CritiqueCode by swapping `@critiquedotsh/cli`. Do not call `critique finish` as a substitute for this harness.
+Same npm org. Different products. Do not install CritiqueCode by swapping `@critiquedotsh/cli`. Native evidence stays on `/review`. `/critique` and `critique_cli` spawn the installed `critique` sidecar when you want that binary.
 
 Docs: [CritiqueCode](https://critique.sh/docs/platform/critique-code) · [Inference API](https://critique.sh/docs/platform/inference-api) · [Critique CLI](https://critique.sh/docs/platform/cli)
 
@@ -87,7 +87,7 @@ Describe the change. Slash lines (`/review`, `/ship`, …) are never sent to the
 4. **`/repair`** runs verified repair on promoted findings. It is not auto-applied chatter.
 5. `none_promoted` means nothing was promoted. It is **not** a correctness proof.
 
-The author can fan out **`critique_task`** workers (`explore` is read-only; `general` / `implement` can write through the same CAS path). Independent review is still `/review`, not a worker. `critique_run` still needs your approval. Workers cannot nest `critique_task`.
+The author can fan out **`critique_task`** workers (`explore` is read-only; `general` / `implement` can write through the same CAS path). Independent native review is still `/review`, not a worker. `critique_cli` spawns the installed Critique CLI sidecar when you ask for that binary. `critique_run` still needs your approval. Workers cannot nest `critique_task` or `critique_cli`.
 
 The TTY shows a wordmark, a compact live status (`thinking` / `write path` / `task explore …`), then a one-line `▸` summary before the reply. It does not stream thinking paragraphs.
 
@@ -103,6 +103,7 @@ critique-code login
 critique-code settings | keys | models
 critique-code review [--depth quick|standard|paranoid] [--focus general,security] [--models ...] [--base <ref>] [--intent <text>] [--cwd <dir>] [--store <dir>]
 critique-code repair <review-run-id> [--store <dir>] [--cwd <dir>] [--models ...]
+critique-code critique [sidecar argv...] [--cwd <dir>]
 critique-code capabilities [--cwd <dir>]
 critique-code skills [--cwd <dir>]
 critique-code import-skills [--cwd <dir>]
@@ -117,6 +118,7 @@ critique-code help
 | `settings` / `keys` / `models` | TUI for route, stored keys, and model ids |
 | `review` | Evidence harness (JSON on stdout) |
 | `repair <id>` | Verified repair for a stored review run |
+| `critique [argv…]` | Spawn the installed Critique CLI sidecar (`critique review --json` by default) |
 | `capabilities` | Discovered local check tools |
 | `skills` | Built-in plus imported Claude Code / Codex / Cursor `SKILL.md` folders |
 | `import-skills` | Copy discovered skills into `~/.critique/code/skills` |
@@ -152,6 +154,8 @@ Type `/` or `/help` for a selectable picker. **Lines that start with `/` never g
 | `/voice off` | Return to the keyboard |
 | `/review` | Evidence harness since the last review checkpoint |
 | `/review all` | Evidence harness on the current tree even if unchanged |
+| `/critique` | Spawn the Critique CLI sidecar (`critique review --json`) |
+| `/critique finish` | Sidecar `finish --repair pack`; apply stays an explicit slash |
 | `/repair` | Verified repair of promoted findings |
 | `/ship` | Review, then end if the controller allows |
 | `/settings` | Keys, route, models |