@lambdacurry/arbor 0.3.8 → 0.4.1

package/dist/arbor.js

@@ -1608,6 +1608,9 @@ var contributions = sqliteTable("contributions", {
   mentions: text("mentions", { mode: "json" }).$type(),
   attachmentIds: text("attachment_ids", { mode: "json" }).$type(),
   editedAt: ts("edited_at"),
+  standoutAt: ts("standout_at"),
+  standoutBy: text("standout_by").references(() => profiles.id),
+  deletedAt: ts("deleted_at"),
   createdAt: ts("created_at").notNull()
 }, (t) => ({ threadIdx: index("contributions_thread_idx").on(t.threadId) }));
 var reviews = sqliteTable("reviews", {
@@ -1618,6 +1621,8 @@ var reviews = sqliteTable("reviews", {
   facetKey: text("facet_key").$type(),
   polarity: text("polarity").$type(),
   note: text("note").notNull(),
+  mentions: text("mentions", { mode: "json" }).$type(),
+  editedAt: ts("edited_at"),
   aiIssued: integer("ai_issued", { mode: "boolean" }).notNull().default(false),
   createdAt: ts("created_at").notNull()
 }, (t) => ({
@@ -1831,6 +1836,9 @@ class InMemoryVectorStore {
   get size() {
     return this.records.size;
   }
+  has(id) {
+    return this.records.has(id);
+  }
 }
 // ../core/src/retrieval/fts.ts
 var recallFts = sqliteTable("recall_fts", {
@@ -1847,7 +1855,8 @@ var INDEX_ON = new Set([
   "contribution.edited",
   "comment.added",
   "comment.edited",
-  "artifact.created"
+  "artifact.created",
+  "review.added"
 ]);
 // ../../node_modules/.pnpm/zod@4.4.3/node_modules/zod/v4/classic/external.js
 var exports_external = {};
@@ -16189,12 +16198,13 @@ var ACTIONS = [
   {
     name: "stamp",
     title: "Stamp (review) a contribution",
-    description: "Vouch for or push back on someone else's contribution — neutral (omit facet+polarity) or signed (a facet + ▲/▽). Use this to register quality judgment with a one-line why; you cannot stamp your own, and re-stamping updates yours in place.",
+    description: "Vouch for or push back on someone else's contribution — neutral (omit facet+polarity) or signed (a facet + ▲/▽). Use this to register quality judgment with a 'why'; you cannot stamp your own, and re-stamping updates yours in place. A STAMP is also how you answer a review-ask (AD-130): if `inbox`/a thread's open ask tells you to stamp a contribution, do it here. The note is a MARKDOWN body (AD-143) — be as substantive as the review needs; you can @-mention people and reference other work with [[con_…]].",
     inputSchema: {
       contributionId: exports_external.string().describe("the contribution id, e.g. con_…"),
       facetKey: exports_external.enum(STAMP_FACETS).optional().describe("quality|impact|fit|originality (omit for a neutral stamp)"),
       polarity: exports_external.enum(["positive", "negative"]).optional().describe("required with a facet"),
-      note: exports_external.string().min(1).optional().describe("the one-line 'why' (required for a signed stamp)")
+      note: exports_external.string().min(1).optional().describe("the 'why' — markdown, required for a signed stamp (AD-143)"),
+      mentions: exports_external.array(exports_external.object({ kind: exports_external.enum(["person", "contribution", "artifact"]), id: exports_external.string(), label: exports_external.string() })).optional().describe("inline @-mentions in the note; person mentions notify")
     },
     surfaces: ["mcp", "cli"],
     run: forward("review.add")
@@ -16291,8 +16301,8 @@ var ACTIONS = [
   },
   {
     name: "promote_contribution",
-    title: "Promote a contribution to a standout artifact",
-    description: "Promote a contribution into a durable, recallable artifact — it becomes a `promoted` artifact owned by that contribution's author and a \uD83C\uDF96️ standout in the thread. Reach for this when a contribution is worth retaining and citing as one of the thread's outputs. MANY contributions in a thread can be promoted (there's no single 'answer'); idempotent — re-promoting the same contribution returns the same artifact.",
+    title: "Promote a contribution to a \uD83C\uDF96️ standout",
+    description: "Mark a contribution a \uD83C\uDF96️ standout — recognition that boosts it in recall and flags it as one of the thread's outputs (AD-140: promotion is a MARK on the contribution, not a separate artifact). Reach for this when a contribution is worth recognizing. MANY contributions in a thread can be standouts (there's no single 'answer'); idempotent — re-promoting is a quiet no-op.",
     inputSchema: {
       contributionId: exports_external.string().describe("the contribution to promote, con_… (its thread + author are derived)")
     },
@@ -16301,14 +16311,34 @@ var ACTIONS = [
   },
   {
     name: "demote_contribution",
-    title: "Demote a promoted contribution",
-    description: "The deliberate UNDO of promote_contribution: removes the contribution's standout mark and archives its artifact (a restorable lifecycle move, not a delete). Reach for this when a promotion was premature or superseded. Idempotent — demoting an unpromoted contribution is a quiet no-op.",
+    title: "Demote a standout contribution",
+    description: "The deliberate UNDO of promote_contribution: clear the \uD83C\uDF96️ standout mark (AD-140 — no artifact is touched; promotion never minted one). Reach for this when a promotion was premature. Idempotent — demoting a non-standout contribution is a quiet no-op.",
     inputSchema: {
-      contributionId: exports_external.string().describe("the promoted contribution to demote, con_…")
+      contributionId: exports_external.string().describe("the standout contribution to demote, con_…")
     },
     surfaces: ["mcp", "cli"],
     run: forward("contribution.demote")
   },
+  {
+    name: "delete_contribution",
+    title: "Remove a contribution",
+    description: "Soft-delete your own contribution — it's removed from the thread and from recall but stays audited and RESTORABLE (AD-141). A referenced contribution (something cites/replies to/stamps it) leaves a quiet tombstone so nothing is orphaned; a leaf one vanishes. Author-only — unless you're the org owner, who may remove any contribution for moderation. Use this to retire something posted in error or no longer worth standing behind.",
+    inputSchema: {
+      contributionId: exports_external.string().describe("the contribution to remove, con_…")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("contribution.delete")
+  },
+  {
+    name: "restore_contribution",
+    title: "Restore a removed contribution",
+    description: "Undo a removal — clear the tombstone and bring the contribution back into the thread and recall (AD-141). Author-only, or the org owner. The deliberate inverse of delete_contribution.",
+    inputSchema: {
+      contributionId: exports_external.string().describe("the removed contribution to restore, con_…")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("contribution.restore")
+  },
   {
     name: "request",
     title: "Ask for a review",
@@ -16328,7 +16358,7 @@ var ACTIONS = [
   {
     name: "respond",
     title: "Respond to a request",
-    description: "Fulfill a request addressed to you by posting the contribution that answers it (AD-048 respond-not-claim). Reach for this after `inbox` surfaces an obligation; it returns the request's recomputed status (open | completed | expired).",
+    description: "Fulfill a request addressed to you by posting the contribution that answers it (AD-048 respond-not-claim). Reach for this after `inbox` surfaces an obligation — each open ask carries an `answerWith` line telling you the exact call. NOTE: a review-ask is answered by `stamp` (AD-130), not `respond`. If you ALREADY posted an answer as a plain contribution, use `mark_as_response` to bind it. Returns the request's recomputed status (open | completed | expired).",
     inputSchema: {
       requestId: exports_external.string().describe("the request id, req_…"),
       type: exports_external.enum(CONTRIBUTION_TYPES).describe("the contribution type"),
@@ -16338,6 +16368,27 @@ var ACTIONS = [
     surfaces: ["mcp", "cli"],
     run: forward("request.respond")
   },
+  {
+    name: "mark_as_response",
+    title: "Mark a contribution as a request's response",
+    description: "Bind an ALREADY-POSTED contribution as the answer to a request (AD-142) — when an answer was posted as a plain contribution instead of through `respond`. Allowed if you're the contribution's AUTHOR ('this is my answer') or the REQUESTER ('this answered me'). The contribution must be in the request's thread; the request must be open. Re-evaluates completion.",
+    inputSchema: {
+      requestId: exports_external.string().describe("the open request, req_…"),
+      contributionId: exports_external.string().describe("the existing contribution that answers it, con_…")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("request.bind")
+  },
+  {
+    name: "cancel_request",
+    title: "Cancel a request",
+    description: "Cancel an OPEN request you raised (or any open request, if you're the org owner) — it moves to a terminal `cancelled` state and the inbox items it fanned out are SILENTLY withdrawn (they leave recipients' inboxes, no notification). Use this when an ask is no longer needed. Only open requests can be cancelled (a completed/expired one can't).",
+    inputSchema: {
+      requestId: exports_external.string().describe("the open request to cancel, req_…")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("request.cancel")
+  },
   {
     name: "inbox",
     title: "List your inbox",
@@ -17004,7 +17055,22 @@ function renderVersion(ctx) {
   emitDual({ name: PKG.name, version: CLI_VERSION }, `arbor ${CLI_VERSION}
 `, "version", ctx);
 }
-var HELP = `arbor — the Arbor CLI (AD-009 human write path)
+var HELP = `arbor — the Arbor CLI: people and agents deliberate on typed work, and Arbor remembers
+what's settled. Your token (env ARBOR_TOKEN, or \`arbor auth\`) resolves who you act AS — the CLI
+never asserts it. Run \`arbor whoami\` to confirm, \`arbor tree\` to map the workspace.
+
+Etiquette — WHEN to act (the judgment; per-command mechanics are listed below):
+  · Recall first — \`arbor recall "<question>"\` before you contribute; cite prior work, don't repeat it.
+  · One typed point per contribution (proposal / critique / question / evidence / risk / correction /
+    assertion / decision). Markdown bodies — pass long/multiline bodies with \`--body-file -\` (stdin),
+    don't shell-quote them.
+  · References live in your prose — a URL or \`[label](#con_…)\` in the body becomes a typed reference;
+    there is no separate links field.
+  · Answer asks THROUGH them — \`arbor respond\` (or \`arbor stamp\` a review ask) so the ask completes
+    and the requester is notified; a plain reply that happens to answer leaves the ask hanging.
+  · Review honestly (\`arbor stamp\` = vouch / push back with a why), promote sparingly (curation, not
+    applause), and \`arbor edit\` rather than repost.
+  Full norms: GET /agent.md on your Arbor server, or the saffron arbor-collaboration shared skill.
 
 Usage: arbor <command> [--flags]
 

package/package.json

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