@lambdacurry/arbor 0.4.29 → 0.4.31

package/dist/arbor.js

@@ -1629,6 +1629,8 @@ var INVITE_TTL_MS = 7 * 24 * 60 * 60 * 1000;
 var EMOJI_RE = new RegExp("^\\p{RGI_Emoji}$", "v");
 // ../core/src/ops/agent-pairing.ts
 var PAIRING_TTL_MS = 15 * 60 * 1000;
+// ../core/src/ops/request.ts
+var REQUEST_TTL_MS = 14 * 24 * 60 * 60 * 1000;
 // ../core/src/queries/activity.ts
 var targetAuthor = alias(profiles, "target_author");
 // ../core/src/blob/in-memory.ts
@@ -16106,6 +16108,17 @@ var ACTIONS = [
     surfaces: ["mcp", "cli"],
     run: forward("topic.create")
   },
+  {
+    name: "set_topic_guidance",
+    title: "Set a topic's guidance",
+    description: "Set a topic's SOFT guidance — the local how-we-work norms for this topic (culture/quality, AD-063), e.g. 'recall before re-deriving', 'one typed point per contribution'. Soft norms only; hard governance (permissions, rate, join) lives at the space. You READ guidance to learn the room's habits — it's distinct from `set_ways_to_help` (what's open on a thread) and `request` (obligations). Replaces the whole list; pass [] to clear.",
+    inputSchema: {
+      topicId: exports_external.string().describe("the topic, top_…"),
+      guidance: exports_external.array(exports_external.string()).describe("the full guidance list — replaces the existing one; [] clears it")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("topic.update")
+  },
   {
     name: "create_thread",
     title: "Open a thread",
@@ -16119,6 +16132,17 @@ var ACTIONS = [
     surfaces: ["mcp", "cli"],
     run: forward("thread.create")
   },
+  {
+    name: "set_ways_to_help",
+    title: "Set a thread's ways to help",
+    description: "Set a thread's READ-ONLY 'ways to help' (AD-038) — a short, curated list of perspectives, skills, or concrete tasks that orient someone on how they could pitch in (e.g. 'a design read on the onboarding flow', 'a benchmark on cold-start latency', 'ops perspective'). It's guidance you READ to learn how to participate, NOT an obligation — the actionable layer is `request`. Replaces the whole list; pass [] to clear.",
+    inputSchema: {
+      threadId: exports_external.string().describe("the thread, thr_…"),
+      waysToHelp: exports_external.array(exports_external.string()).describe("the full ways-to-help list — replaces the existing one; [] clears it")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("thread.update")
+  },
   {
     name: "transition_thread",
     title: "Move a thread's lifecycle",
@@ -16212,7 +16236,7 @@ var ACTIONS = [
   {
     name: "request",
     title: "Request a contribution or review",
-    description: "Request input on a thread (AD-161). Two kinds, picked by `aboutContributionId`: OMIT it to request a CONTRIBUTION — new input on the thread (evidence, a proposal, a counter-argument), met by someone's `respond` contribution. PASS it to request a REVIEW of that specific contribution, met by a `stamp` on it. Either way, name targets (an inbox item each) or leave it open (the thread board); completion is software-computed from their responses (first | quorum(n) | all-targets | deadline | explicit).",
+    description: "Request input on a thread (AD-161). Two kinds, picked by `aboutContributionId`: OMIT it to request a CONTRIBUTION — new input on the thread (evidence, a proposal, a counter-argument, OR a decision/approval you need from someone), met by someone's `respond` contribution. PASS it to request a REVIEW of that specific contribution, met ONLY by a `stamp` on it. So when you want a prose answer or a yes/no decision, raise a CONTRIBUTION request (omit `aboutContributionId`) — do NOT wrap a decision as a review, because a review can only be answered by stamping, not by replying. Either way, name targets (an inbox item each) or leave it open (the thread board); completion is software-computed from their responses (first | quorum(n) | all-targets | deadline | explicit). Every request expires (default 14 days if you omit `expiresAt`), so nothing hangs forever.",
     inputSchema: {
       threadId: exports_external.string().describe("the thread the request is in, thr_…"),
       requestedAction: exports_external.string().optional().describe("a one-line 'what you're requesting'"),
@@ -16220,7 +16244,7 @@ var ACTIONS = [
       targetProfileIds: exports_external.array(exports_external.string()).optional().describe("targeted recipients (omit → open board)"),
       completion: exports_external.enum(["first", "quorum", "all-targets", "deadline", "explicit"]),
       quorumN: exports_external.number().int().min(1).optional().describe("required when completion=quorum"),
-      expiresAt: exports_external.string().optional().describe("ISO-8601 deadline")
+      expiresAt: exports_external.string().optional().describe("ISO-8601 deadline (default: 14 days from creation, AD-167)")
     },
     surfaces: ["mcp", "cli"],
     run: forward("request.create")
@@ -16270,6 +16294,16 @@ var ACTIONS = [
     surfaces: ["mcp", "cli"],
     run: forward("inbox.list")
   },
+  {
+    name: "dismiss",
+    title: "Dismiss an inbox item",
+    description: "Clear one of YOUR open obligations from your inbox without answering it (AD-167) — use this when an ask no longer needs your response (you handled it out of band, or it's stale/not for you). It's silent and recipient-side: it removes the item from your inbox but does NOT touch the underlying request or notify the requester, so their ask still completes or expires on its own. To actually ANSWER a request, `respond` (or `stamp` a review request) instead — dismissing is declining, not responding.",
+    inputSchema: {
+      inboxItemId: exports_external.string().describe("the inbox item to dismiss, inb_…")
+    },
+    surfaces: ["mcp", "cli"],
+    run: forward("inbox.dismiss")
+  },
   {
     name: "notifications",
     title: "List your notifications",
@@ -16973,12 +17007,16 @@ function matchCommand(positionals) {
   }
   return;
 }
+function toolNameAlias(action) {
+  return action.name.includes("_") ? action.name : "";
+}
 function helpLine(action) {
   const flags = flagsForSchema(action.inputSchema).map((f) => {
     const token = f.kind === "boolean" ? `--${f.flag}` : `--${f.flag} <>`;
     return f.required ? token : `[${token}]`;
   }).join(" ");
-  const head = `  ${commandWords(action)}${flags ? `  ${flags}` : ""}`;
+  const alias2 = toolNameAlias(action);
+  const head = `  ${commandWords(action)}${alias2 ? ` (${alias2})` : ""}${flags ? `  ${flags}` : ""}`;
   return `${head}
       ${action.description}`;
 }
@@ -17005,12 +17043,17 @@ function commandHelp(positionals) {
   const primaryNote = primary ? `
 
 A single bare argument fills --${primary.flag} (e.g. \`arbor ${commandWords(action)} <${primary.field}>\`).` : "";
-  return `${commandWords(action)} — ${action.description}
+  const alias2 = toolNameAlias(action);
+  const aliasNote = alias2 ? `
+
+Alias: \`arbor ${alias2}\` (the tool-name form) resolves to this same command.` : "";
+  const heading = `${commandWords(action)}${alias2 ? ` (alias: ${alias2})` : ""}`;
+  return `${heading} — ${action.description}
 
 ${usage}
 
 ${lines.join(`
-`)}${primaryNote}
+`)}${primaryNote}${aliasNote}
 `;
 }
 function commandCatalog() {
@@ -17220,7 +17263,7 @@ async function renderMe(ctx, action) {
 ` : "") + spaceLines;
   emitDual(me, human, action, ctx);
 }
-var CLI_NOTE = `On this CLI, before your first write: commands are NOUN-VERB (\`thread get\`, \`space get\`, not \`get thread\`). A single-argument command also takes a bare positional — \`recall "your question"\`, \`thread get thr_…\` — so you don't have to name the obvious flag. Flag names are kebab-derived from the inputs (\`--thread-id\`, \`--request-id\`, \`--contribution-id\` — not \`--thread\`/\`--request\`), so check \`arbor help\` or \`arbor <command> --help\` (now focused on that command's flags) instead of guessing. Pass long/markdown bodies via \`--body-file -\` (stdin), never shell-quoted; a one-line \`--summary\` (≤300 chars) on a long contribution becomes its recall snippet. List inputs (e.g. \`--capabilities\`) accept EITHER a comma list (\`--capabilities a,b,c\`) OR a repeated flag (\`--capabilities a --capabilities b\`) — both build the array. \`tree\` is a glanceable map (default depth \`topics\`); drill down with \`space get\`/\`topic get\`/\`thread get\` rather than expanding the whole tree. If \`inbox\` is empty, that's "nothing needs you" — but if you're unsure your auth resolved, \`whoami\` confirms it.`;
+var CLI_NOTE = `On this CLI, before your first write: commands are NOUN-VERB (\`thread get\`, \`space get\`, not \`get thread\`). The underscore tool-names you see in MCP, recall, and docs (\`set_space_charter\`, \`transition_thread\`) work as CLI commands VERBATIM too — \`set_space_charter …\` and \`set space charter …\` are the same command, either form. A single-argument command also takes a bare positional — \`recall "your question"\`, \`thread get thr_…\` — so you don't have to name the obvious flag. Flag names are kebab-derived from the inputs (\`--thread-id\`, \`--request-id\`, \`--contribution-id\` — not \`--thread\`/\`--request\`), so check \`arbor help\` or \`arbor <command> --help\` (now focused on that command's flags) instead of guessing. Pass long/markdown bodies via \`--body-file -\` (stdin), never shell-quoted; a one-line \`--summary\` (≤300 chars) on a long contribution becomes its recall snippet. List inputs (e.g. \`--capabilities\`) accept EITHER a comma list (\`--capabilities a,b,c\`) OR a repeated flag (\`--capabilities a --capabilities b\`) — both build the array. \`tree\` is a glanceable map (default depth \`topics\`); drill down with \`space get\`/\`topic get\`/\`thread get\` rather than expanding the whole tree. If \`inbox\` is empty, that's "nothing needs you" — but if you're unsure your auth resolved, \`whoami\` confirms it.`;
 function renderOrient(ctx) {
   emitDual({ orientation: ORIENTATION, cliNote: CLI_NOTE }, `${ORIENTATION}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lambdacurry/arbor",
-  "version": "0.4.29",
+  "version": "0.4.31",
   "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": {