@critiquedotsh/harness 0.1.13 → 0.1.14

package/README.md

@@ -85,7 +85,7 @@ critique-code remote --slack --anywhere
 critique-code slack
 ```
 
-Drive it from the website instead. Open [critique.sh/code](https://critique.sh/code), click **Connect this PC**, then paste the printed code on this machine:
+Drive it from the website instead. Open [critique.sh/connect](https://critique.sh/connect), click **Connect this PC**, then paste the printed code on this machine:
 
 ```bash
 critique-code connect K7M2-9QWX
@@ -98,11 +98,13 @@ Describe the change. Slash lines (`/review`, `/ship`, …) are never sent to the
 ## What a session does
 
 1. **Author** implements in the working tree (writes go through a content-addressed apply path).
-2. You can ask the model to run a workspace command via `critique_run`. **You** approve or deny each request. Denied means nothing runs. Output is not Evidence.
+2. You can ask the model to run a workspace command via `critique_run`. **You** approve or deny each request. Denied means nothing runs. Networked runs are disabled unless a controller explicitly provides an enforced sandbox. Output is not Evidence.
 3. **`/review` or `/ship`** starts the evidence harness. Author chat is withheld from the reviewer.
 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.
 
+EOF attempts to review dirty work, while `/exit` records an incomplete session without claiming completion. The session store keeps only the task contract, review handoff, capsule digest, and bounded status—not the author transcript. A later invocation resumes only when the repository still matches that digest; stale state is surfaced explicitly. Partial or failed reports cannot satisfy `/done` or `/ship` without an auditable user override.
+
 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.
@@ -135,7 +137,7 @@ critique-code help
 | `critique-code` / `chat` | Interactive author session |
 | `web` | Local browser UI on `127.0.0.1` (same author kernel; no TTY required) |
 | `remote` | Phone pairing to this laptop: LAN PIN, optional `--anywhere` tunnel. Not Critique Cloud. |
-| `connect [CODE]` | Register this PC on critique.sh/code. The website is a remote; the kernel stays here. |
+| `connect [CODE]` | Register this PC on critique.sh/connect. The website is a remote; the kernel stays here. |
 | `slack` / `telegram` | Outbound bots. DM the agent from those apps; the kernel stays in this process. |
 | `login` | Browser device approval; connect Critique Inference |
 | `settings` / `keys` / `models` | TUI for route, stored keys, and model ids |
@@ -180,6 +182,10 @@ Type `/` or `/help` for a selectable picker. **Lines that start with `/` never g
 | `/voice` | Record one spoken prompt (Qwen3 ASR) |
 | `/voice on` | Keep listening after each reply |
 | `/voice off` | Return to the keyboard |
+| `/goal <objective>` | Set one durable author objective; include the intended end state and proof loop |
+| `/goal` / `/goal status` | Show the objective, lifecycle, and latest native review state |
+| `/goal edit <objective>` | Change and resume the current objective |
+| `/goal pause` / `/goal resume` / `/goal clear` | Control or remove the durable objective |
 | `/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`) |
@@ -197,6 +203,12 @@ Spoken `review`, `repair`, `ship`, and `exit` match the typed commands when voic
 
 Unknown `/foo` is rejected in the TUI. It is not forwarded as chat.
 
+### Durable goals
+
+`/goal` keeps one controller-owned objective with the resumable author session; it is restored after a process restart without retaining the raw author transcript. An active goal autonomously takes bounded checkpoint turns until it pauses, requests final verification, or becomes genuinely blocked. Every eight autonomous turns, CritiqueCode compacts the author context and opens a fresh author kernel with the durable task, live workspace state, controller evidence, and the active goal—so a long run does not depend on an ever-growing transcript. There is no implicit one-day ceiling for an interactive goal.
+
+The author cannot mark a goal complete. It can only request final verification through `critique_goal`; the controller then runs validation and native `/review` on the current workspace. A qualifying clean result records the goal as complete; an unresolved completion decision records it as blocked. Pausing a goal preserves it but stops autonomous turns and goal injection.
+
 ## Voice mode
 
 Talk to the author and the reviewer. `/voice` records one clip (Enter to stop). `/voice on` keeps listening after each reply. `/voice off` returns to the keyboard. `critique-code --voice` starts already listening.
@@ -269,7 +281,7 @@ The agent is this process on this laptop. Phone, Slack, Telegram, and the websit
 1. Leave the machine awake with the session running.
 2. Same Wi-Fi: `critique-code remote`, open the LAN URL on the phone, enter the PIN from the terminal.
 3. Anywhere: DM the Slack or Telegram bot (`critique-code slack` / `critique-code telegram` / `--slack`). Those open outbound sockets. No inbound port.
-4. Website: `critique-code connect CODE` after `critique-code login` claims the PC from [critique.sh/code](https://critique.sh/code). The site relays prompts and approvals; the kernel stays here.
+4. Website: `critique-code connect CODE` after `critique-code login` claims the PC from [critique.sh/connect](https://critique.sh/connect). The site relays prompts and approvals; the kernel stays here.
 5. Optional `--anywhere` uses **your** `cloudflared` or `ngrok`. The tunnel is a pipe. Writes still happen in this working tree.
 
 Slack Socket Mode needs `SLACK_BOT_TOKEN` (`xoxb-`) and `SLACK_APP_TOKEN` (`xapp-`) with message events. Telegram needs `TELEGRAM_BOT_TOKEN`. Optional allowlists: `CRITIQUE_CODE_PORTAL_USERS`, `CRITIQUE_CODE_PORTAL_CHATS`.
@@ -292,7 +304,7 @@ Project `REVIEW_GUIDELINES.md` is loaded as a review constraint. `AGENTS.md`, `C
 ## Safety
 
 - The model cannot pick a working directory, open a network path, or run a process on its own.
-- `critique_run` is the only workspace exec path. You approve or deny each call. Output is not Evidence.
+- `critique_run` is the only workspace exec path. You approve or deny each call; networked commands require an enforced controller sandbox and are disabled by default. Output is not Evidence.
 - Promotion of findings stays on `/review` and `/ship`.
 - Named checks are controller-owned. Author check output is not Evidence.
 - `none_promoted` is not a proof that the tree is correct.