@macintacos/caret 0.1.3 → 0.3.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "caret",
-  "version": "0.1.3",
+  "version": "0.3.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

@@ -95,8 +95,8 @@ defaults, and the environment variables is in
 
 ## Reporting bugs
 
-- `caret discovery` prints a one-shot, read-only diagnostics snapshot of your install —
-  ready to paste into a bug report (`caret discovery --json` for machine-readable output).
+- `/caret:discovery` prints a one-shot, read-only diagnostics snapshot of your install —
+  ready to paste into a bug report.
 - `/caret:debug` reviews the current session's plans and recent errors.
 
 Details, plus how to scrub logs with `caret redact`, are in

package/commands/demo.md

@@ -2,10 +2,11 @@
 description: Demo caret by presenting a short fake plan via ExitPlanMode
 ---
 
-Read the shared fake-plan fixture at `${CLAUDE_PLUGIN_ROOT}/scripts/dev/fake-plan.md` and
-present its contents **verbatim** to the user by calling `ExitPlanMode` with that markdown
-as the `plan` argument. This is the same fixture `mise run dev` seeds, so the demo and the
-dev environment draw their plan from one source of truth. Do **not** do any real work,
+Read the shared fake-plan fixture at
+`${CLAUDE_PLUGIN_ROOT}/scripts/tasks/dev/fake-plan.md` and present its contents
+**verbatim** to the user by calling `ExitPlanMode` with that markdown as the `plan`
+argument. This is the same fixture `mise run dev` seeds, so the demo and the dev
+environment draw their plan from one source of truth. Do **not** do any real work,
 research, or file edits — this is only to exercise the review flow. If the fixture can't
 be read, fall back to inventing a short, plausible-but-fake plan (a Context section, an
 Approach section, and a couple of Steps).