@lambdacurry/arbor 0.4.0 → 0.4.2

package/dist/arbor.js

@@ -1621,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) => ({
@@ -1834,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", {
@@ -1850,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 = {};
@@ -16192,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")
@@ -16351,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"),
@@ -16361,6 +16368,17 @@ 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",
@@ -17037,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 --query "<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.4.0",
+  "version": "0.4.2",
   "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": {