@lambdacurry/arbor 0.4.20 → 0.4.22

package/dist/arbor.js

@@ -15996,9 +15996,9 @@ var ORIENTATION = `Arbor is your team's deliberation room and shared memory —
 1. RECALL FIRST. Run \`recall\` before re-deriving or restating anything — it may already be settled; cite prior work ([label](#con_…)) and build on it. Empty recall is itself worth noting. WHY: a room where everyone re-derives is just a chat log.
 2. CONTRIBUTE typed points — ONE point per contribution, with the type that names your move (proposal / critique / question / evidence / risk / correction / assertion / decision). Markdown welcome; put references IN your prose (a URL or [label](#con_…) becomes a navigable reference — there's no separate links field). WHY: one typed point is reviewable on its own.
 3. ANSWER through asks. When \`inbox\` or a thread shows an open request you can meet, answer THROUGH it — \`respond\` to it, or \`stamp\` the contribution a review-ask is about — so it completes and the requester is notified. WHY: a plain reply that merely happens to answer leaves their ask hanging (the most common failure).
-4. REVIEW honestly. \`stamp\` to vouch or push back on a point with a one-line why (you can't stamp your own work — ask via \`request\`). Promote sparingly. WHY: a standout is curation, not applause — if everything's promoted, nothing is.
+4. REVIEW honestly; promote the standout, sparingly. \`stamp\` to vouch or push back with a one-line why (you can't stamp your own work — ask via \`request\`). PROMOTE a contribution/artifact only when it's the standout the org should find FIRST (the \uD83C\uDF96️). WHY: promotion is curation, not applause — and it's about an OUTPUT, never a whole thread (a thread RESOLVES; it is never "promoted").
 5. EDIT, don't repost. \`edit\` your own contribution to sharpen it; the record stays audited. A genuinely different point is a NEW contribution.
-6. OPEN STRUCTURE sparingly. Check \`tree\` first and prefer an existing thread; \`create_topic\`/\`create_thread\` only when work truly doesn't fit, named by its OBJECTIVE with your first contribution. Filed somewhere wrong or concluded? \`transition_thread --to archived\` and reopen where it belongs. WHY: structure is scarce — clutter makes the room harder to read.
+6. OPEN STRUCTURE sparingly, and CLOSE it when done. Check \`tree\` first and prefer an existing thread; \`create_topic\`/\`create_thread\` only when work truly doesn't fit, named by its OBJECTIVE with your first contribution. When a thread reaches its conclusion, \`transition_thread --to resolved\` (done); if it was opened in the wrong place, \`--to archived\` and reopen where it belongs. WHY: structure is scarce — both clutter AND open threads no one closes make the room harder to read.
 
 Run \`arbor help\` (or read the MCP tool list) for the exact command/flags — those stay generated from the live action surface, so they're always current.`;
 function forward(operation) {
@@ -16114,10 +16114,10 @@ var ACTIONS = [
   {
     name: "transition_thread",
     title: "Move a thread's lifecycle",
-    description: "Move a thread along its deliberate lifecycle (AD-068). Most often `archived` — conclude a thread, or retire one opened in the wrong place (archive it, then open a fresh one where it belongs; an archived thread drops out of normal recall as historical, but stays recoverable and can be restored to `active`). You can also mark it `stuck`/`needs-review`/`promoted`. Illegal jumps are rejected; whoever works the thread keeps its status current.",
+    description: "Move a thread along its deliberate lifecycle (AD-068/159). The two CLOSED states are about the WORK, not curation: `resolved` = the deliberation reached its conclusion (done) — use this to close a thread you've settled; `archived` = retire/shelve it (e.g. opened in the wrong place — archive it, then open a fresh one where it belongs). Both drop out of normal recall and stay recoverable to `active`. You can also flag it `stuck`/`needs-review` while it's open. NOTE: a standout OUTPUT gets promoted (a \uD83C\uDF96️ contribution/artifact via `promote_contribution`) — the THREAD just resolves; don't look for a 'promote thread'. Illegal jumps are rejected.",
     inputSchema: {
       threadId: exports_external.string().describe("the thread to move, thr_…"),
-      to: exports_external.string().describe("target status: active|needs-review|stuck|promoted|archived"),
+      to: exports_external.string().describe("target status: active|needs-review|stuck|resolved|archived"),
       reason: exports_external.string().optional().describe("optional one-line why, recorded on the event")
     },
     surfaces: ["mcp", "cli"],
@@ -16325,7 +16325,7 @@ var ACTIONS = [
     title: "Read a thread",
     description: "Read the full state of the thread you're working in — objective, every contribution + stamp, and its OPEN REQUESTS. Load this before contributing; if an open request matches what you're about to say, respond (or `stamp` the card it's about) so the request completes. On a LONG thread, page the contributions with contribLimit/contribCursor (follow contributionPage.nextCursor) to bound how much you load at once.",
     inputSchema: {
-      id: exports_external.string().describe("the thread id, e.g. thr_…"),
+      threadId: exports_external.string().describe("the thread id, e.g. thr_…"),
       contribLimit: exports_external.number().int().positive().optional().describe("max contributions to return (AD-151 keyset paging) — omit to load the whole thread; set on a long thread to bound context"),
       contribCursor: exports_external.string().optional().describe("continuation cursor from a previous page's contributionPage.nextCursor")
     },
@@ -16526,7 +16526,7 @@ var ACTIONS = [
     title: "Read a space",
     description: "Read one space by id — its details, the topics under it, and the full MEMBER roster: who's here, their role, their capabilities, and each member's space charter (how they operate in THIS space, AD-152) plus their identity charter. Use it to understand who you're collaborating with and how to work with them before you contribute (tree gives the lighter roster across the whole workspace; this zooms into one space with the full how-they-work picture). Space-access gated, like every read.",
     inputSchema: {
-      id: exports_external.string().min(1).describe("the space id")
+      spaceId: exports_external.string().min(1).describe("the space id")
     },
     surfaces: ["mcp", "cli"],
     run: forward("space.get")
@@ -16536,7 +16536,7 @@ var ACTIONS = [
     title: "Read a topic",
     description: "Read one topic by id — its details + the threads under it. Use it to zoom into a single topic (tree gives the whole workspace). Space-access gated, like every read.",
     inputSchema: {
-      id: exports_external.string().min(1).describe("the topic id")
+      topicId: exports_external.string().min(1).describe("the topic id")
     },
     surfaces: ["mcp", "cli"],
     run: forward("topic.get")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lambdacurry/arbor",
-  "version": "0.4.20",
+  "version": "0.4.22",
   "description": "The Arbor CLI — a shared workspace for people and agents. The human + headless-agent write path over Arbor's guarded operation surface.",
   "type": "module",
   "bin": {