@clearlysh/beehaven 0.8.25 → 0.8.27

package/dist/build-channel.js

@@ -53,9 +53,9 @@ export const PUBLIC_BUILD = true;
  * ⚠ REWRITTEN IN `dist/` AT BUILD TIME, like `PUBLIC_BUILD`. `unstamped` is what a source checkout
  * carries and what `tsx`/`vitest` see, and it is honest: nothing has stamped them.
  */
-export const BUILD_SHA = '4f251482a5c6-dirty';
+export const BUILD_SHA = 'db2b3eaeb90b';
 /** ISO-8601 minute precision, UTC. Rewritten in `dist/` by `scripts/stamp-build-channel.mjs`. */
-export const BUILD_TIME = '2026-10-06T06:45Z';
+export const BUILD_TIME = '2026-10-07T02:00Z';
 /**
  * The build identity as one short string, for `--version`.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clearlysh/beehaven",
-  "version": "0.8.25",
+  "version": "0.8.27",
   "description": "Beehaven CLI — command your Clearly workspace, agents, and canvas from the terminal",
   "private": false,
   "type": "module",

package/skills/clearly-agent/SKILL.md

@@ -75,6 +75,17 @@ the admitted agent in the workspace, and soul reads/updates report whether the d
 wearing the drawing or a preset. If the capability line is absent, it is disabled for that
 deployment; the existing companion and presets remain available.
 
+## End with a handoff
+
+```bash
+beehaven agent handoff "what you did · what is next · anything blocked"
+```
+
+The handoff is the note your next login, or the next agent you hand the work to, reads first,
+under **Last time you were here**. Write it for a colleague who has none of your context: what changed,
+where it is (ticket keys, document titles), what is next and what is blocked. It ends the work session
+and keeps your identity bound. Without one, the next brief can show only the session's label and counts.
+
 ⚠ **Do not call `agent-login` immediately after `beehaven agent login`.** The RPC is an alias of
 `agent-session-start`; doing both creates two sessions. Call it directly only when deliberately starting
 or resuming an additional workspace session.
@@ -118,8 +129,8 @@ item queued. Every comment/description write returns `mentions`, `agentsQueued`
 `beehaven comment <ref>` takes any id, key or exact title and the surface's anchor:
 `--quote` (document passage) · `--slide 3` (deck, required) · `--cell B4` / `--cell "Tab!B4"` (sheet) ·
 `--column "In review"` (board) · `--pin <id>` or `--x/--y` (canvas) · `--reply <id>`. An anchor a
-surface cannot carry is **refused**, never dropped. Over MCP: `clearly_write { type:"comment",
-target, content, fields }`, `clearly_read { type:"comment", target }`, and `target:"@me"` for mentions.
+surface cannot carry is **refused**, never dropped. Over MCP: `clearly_comment { target, content,
+fields }`, `clearly_read { type:"comment", target }`, and `target:"@me"` for mentions.
 
 ## Inbox — people and agents message you, and you message them
 
@@ -140,7 +151,7 @@ beehaven inbox who                               # every handle you can put in <
 
 Over MCP, `type: "message"` on the same tools: `clearly_read { type: "message", target: "@inbox" }`
 lists your threads (`box`, `query`), `target: "@people"` lists who you can message, and a thread id
-opens it (marks read). `clearly_write { type: "message", fields: { to: ["ada"] }, content }` starts a
+opens it (marks read). `clearly_comment { type: "message", fields: { to: ["ada"] }, content }` starts a
 thread; with `target: <threadId>` it replies. `clearly_edit { changes: { read | starred | muted } }`
 changes your view; `clearly_delete` archives (`restore: true` brings it back).
 

package/skills/clearly-canvas/authoring.md

@@ -163,11 +163,11 @@ the backing shows through as dark wedges at the corners.
 
 ### Images from MCP
 
-The seven artifact MCP tools do not upload local binary files or dispatch `canvas-act`.
+The artifact MCP tools do not upload local binary files or dispatch `canvas-act`.
 For an image already reachable by an absolute URL, read the composition with
 `clearly_read {type:"composition",target:<id>}`; append an image node
 `{id,type:"image",src,x,y,w,h,fit:"contain",parentId?}` to the returned complete node
-array; then call `clearly_write {type:"composition",target:<id>,content:<JSON array>,
+array; then call `clearly_replace {type:"composition",target:<id>,content:<JSON array>,
 expectedRev:<canvasNodesRev>}`. Preserve every existing node. A stale revision is a
 merge prompt, never a reason to drop `expectedRev`. `clearly_edit` can change an
 existing image's `src`, `fit` or geometry, but cannot create a node. For a local file,
@@ -212,8 +212,8 @@ MCP's artifact tools are split by operation:
 
 - `clearly_catalog {type:"composition"}` exposes the current schemas.
 - `clearly_read` returns nodes and `canvasNodesRev`.
-- `clearly_write` creates a composition or replaces its full node array; use
-  `expectedRev` from the read for replacement.
+- `clearly_create {type:"composition"}` makes a composition; `clearly_replace` replaces its full
+  node array — pass `expectedRev` from the read.
 - `clearly_edit` patches existing nodes with `changes:{ids,patch}`.
 
 Canvas action dispatch and targeted pixels use the CLI. Do not invent

package/skills/index.json

@@ -17,7 +17,7 @@
       "project-plans.md",
       "review.mjs"
     ],
-    "sha": "df3ef3200c38abdf"
+    "sha": "8b1890ca7588af6c"
   },
   {
     "name": "agent-home",
@@ -81,6 +81,6 @@
     "files": [
       "SKILL.md"
     ],
-    "sha": "9e94e53b90ded575"
+    "sha": "c16e1b5d08dbd669"
   }
 ]