@macintacos/caret 0.4.1 → 0.6.0

package/.claude-plugin/plugin.json

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

@@ -15,10 +15,7 @@ Want to develop caret rather than use it? Start with [CONTRIBUTING.md](CONTRIBUT
 
 ## Screenshots
 
-<!-- TODO(EXC-666): review-UI screenshots — plan view + inline annotation,
-request-changes flow, multi-session switcher. -->
-
-_Review-UI screenshots coming soon._
+![caret review UI with an inline annotation, both themes](doc/assets/caret-review-ui.png)
 
 ## Install
 

package/commands/demo.md

@@ -2,14 +2,13 @@
 description: Demo caret by presenting a short fake plan via ExitPlanMode
 ---
 
-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).
+Read the short demo-plan fixture at `${CLAUDE_PLUGIN_ROOT}/scripts/tasks/dev/demo-plan.md`
+and present its contents **verbatim** to the user by calling `ExitPlanMode` with that
+markdown as the `plan` argument. This is a small, self-contained plan meant only to show
+off the review flow — `mise run dev` seeds a different, larger fixture. 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).
 
 This triggers caret's `PermissionRequest`/`ExitPlanMode` hook, which opens the plan in a
 local browser UI for inline review. When the user approves or requests changes there, the