@macintacos/caret 0.8.1 → 0.9.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "caret",
-  "version": "0.8.1",
+  "version": "0.9.0",
   "description": "Review, annotate, and approve Claude Code plans in a local web UI.",
   "author": { "name": "macintacos" },
   "homepage": "https://github.com/macintacos/caret",

package/README.md

@@ -38,11 +38,17 @@ then try `/caret:demo`, which presents a short fake plan to exercise the flow.
 
 ### Updating and uninstalling
 
-**Update.** In Claude Code, run `claude plugin update caret@caret` and restart. In
-OpenCode, caret toasts you at startup when a newer release is out; delete OpenCode's
-cached copy — `rm -rf ~/.cache/opencode/node_modules/@macintacos/caret` — and restart to
-take it, or pin the version in OpenCode's config
-(`"plugin": ["@macintacos/caret@<version>"]`) and bump that when you want to move.
+**Update.** One command for every agent:
+
+```sh
+bunx --no-cache @macintacos/caret@latest install --refresh
+```
+
+`--target` pins the agents the same way it does on install, and restarting each one
+applies the update. In OpenCode, caret toasts you at startup when a newer release is out;
+a plain `install` at a terminal runs its own check against npm and asks before taking it.
+See [`doc/ADVANCED.md`](doc/ADVANCED.md#how-it-works) for the by-hand equivalents and for
+pinning a version in OpenCode's config.
 
 **Uninstall.** The same command, one flag:
 
@@ -69,6 +75,11 @@ prompt. There you:
 A single local daemon serves every session, so concurrent plans queue up in one tab behind
 a switcher.
 
+**In OpenCode**, you don't have to wait to be intercepted: caret registers a
+`caret_review_plan` tool your agent can call directly, so a skill of your own can route
+its approval step through the same review UI. Claude Code has no equivalent — see
+[`doc/ADVANCED.md`](doc/ADVANCED.md#calling-the-review-tool-from-your-own-skill).
+
 ## Configuration
 
 caret runs with sensible defaults and needs no configuration. To tune it, it reads an