@macintacos/caret 1.4.1 → 1.5.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "caret",
-  "version": "1.4.1",
+  "version": "1.5.0",
   "description": "Review, annotate, and approve Claude Code plans in a local web UI.",
   "author": { "name": "macintacos" },
   "homepage": "https://github.com/macintacos/caret",
@@ -15,6 +15,7 @@
     "approval",
     "annotation"
   ],
+  "types": "./mod/band.d.ts",
   "mcpServers": {
     "caret": {
       "command": "${CLAUDE_PLUGIN_ROOT}/bin/caret",

package/README.md

@@ -90,9 +90,10 @@ your browser instead of the terminal prompt. There you:
 
 - **Read** the plan as rendered HTML.
 - **Annotate** — select any passage to attach an inline comment.
-- **Decide** — **Approve** (optionally also switching the session into accept-edits or
-  auto mode) or **Request changes**, which sends your comments back to the agent to revise
-  and re-present.
+- **Decide** — **Approve** — with any comments you've left, applied without another
+  planning round (optionally also switching the session into accept-edits or auto mode) or
+  **Request changes**, which sends your comments back to the agent to revise and
+  re-present.
 
 > [!TIP]
 > You don't have to wait to be intercepted: `/caret:plan <what you want done>` asks the

package/commands/doctor.md

@@ -3,14 +3,14 @@ description: Diagnose this caret install — run caret doctor, relay each failin
 ---
 
 caret's `doctor` subcommand renders a verdict over a one-shot, read-only snapshot of the
-local install: a `checks:` block naming what is wrong and how to fix it, then the state it
-read that from — running caret processes, daemon identity, lock/port state, effective
-settings, review counts, the agent adapter's install-state probe (plugin version, enabled
-state, and whether a manual hook sits in the agent's user settings), log sizes and error
-counts, recent failures grouped by review with their codes, install/runtime info, and
-system basics. The report is **always redacted** (home paths become `~`, usernames in
-foreign home paths are censored) and never contains plan, prompt, or feedback bodies, nor
-any log message, error or stack text — it exists to be shared.
+local install: the failing checks first, each with the command that fixes it, then the
+passing ones, then the state it read them from — running caret processes, daemon identity,
+lock/port state, effective settings, review counts, the agent adapter's install-state
+probe (plugin version, enabled state, and whether a manual hook sits in the agent's user
+settings), log sizes and error counts, recent failures grouped by review with their codes,
+install/runtime info, and system basics. The report is **always redacted** (home paths
+become `~`, usernames in foreign home paths are censored) and never contains plan, prompt,
+or feedback bodies, nor any log message, error or stack text — it exists to be shared.
 
 ## 1. Run it
 
@@ -47,7 +47,7 @@ one. What each id means:
 | `opencode-caret-version` | OpenCode would load a caret behind the published one | the check's remedy verbatim |
 
 An `unknown` check is not a failure: it names its own `reason` — no network, an unreadable
-config, or a report section that never collected, which also shows as `<name> error: …`
+config, or a report section that never collected, which also shows as an `error` line
 (`"error": "…"` under `--json`) and leaves the check with no detail. A doctor run offline
 reaching one is the normal case; present it as-is rather than treating it as a failure of
 this command. A daemon that is simply not running is not one of these — it reports