@lambdacurry/arbor 0.4.6 → 0.4.7

package/dist/arbor.js

@@ -1861,8 +1861,6 @@ var recallFts = sqliteTable("recall_fts", {
 var INDEX_ON = new Set([
   "contribution.added",
   "contribution.edited",
-  "comment.added",
-  "comment.edited",
   "artifact.created",
   "review.added",
   "thread.created",
@@ -16203,7 +16201,7 @@ 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 '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_…]].",
+    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 respond to a review request (AD-130): if `inbox`/a thread's open request 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)"),
@@ -16336,11 +16334,11 @@ var ACTIONS = [
   {
     name: "request",
     title: "Ask for a review",
-    description: "Ask others to review work in a thread — name targets (an inbox item each) or leave it open (the thread board). Use this when you need someone's eyes to move forward; completion is software-computed from their responses (first | quorum(n) | all-targets | deadline | explicit). Review-only (AD-130): a review placed on the asked-about contribution counts as a response.",
+    description: "Request a review of work in a thread — name targets (an inbox item each) or leave it open (the thread board). Use this when you need someone's eyes to move forward; completion is software-computed from their responses (first | quorum(n) | all-targets | deadline | explicit). Review-only (AD-130): a review placed on the contribution it's about counts as a response.",
     inputSchema: {
-      threadId: exports_external.string().describe("the thread the ask is in, thr_…"),
+      threadId: exports_external.string().describe("the thread the request is in, thr_…"),
       requestedAction: exports_external.string().optional().describe("a one-line 'what'"),
-      aboutContributionId: exports_external.string().optional().describe("card-scoped ask: the contribution this is about, con_… (must be in the thread; badges that card)"),
+      aboutContributionId: exports_external.string().optional().describe("card-scoped request: the contribution this is about, con_… (must be in the thread; badges that card)"),
       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"),
@@ -16352,7 +16350,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 — 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).",
+    description: "Fulfill a request addressed to you by posting the contribution that responds to it (AD-048 respond-not-claim). Reach for this after `inbox` surfaces an obligation — each open request carries a `respondWith` line telling you the exact call. NOTE: a review request is met by `stamp` (AD-130), not `respond`. If you ALREADY posted a response 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"),
@@ -16376,7 +16374,7 @@ var ACTIONS = [
   {
     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).",
+    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 a request 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_…")
     },
@@ -16442,7 +16440,7 @@ var ACTIONS = [
   {
     name: "thread_get",
     title: "Read a thread",
-    description: "Read the full state of the thread you're working in — objective, every contribution/stamp/comment, and its OPEN ASKS. Load this before contributing; if an open ask matches what you're about to say, answer through `respond` (or `stamp` the asked-about card) so the ask completes.",
+    description: "Read the full state of the thread you're working in — objective, every contribution/stamp/comment, 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.",
     inputSchema: {
       id: exports_external.string().describe("the thread id, e.g. thr_…")
     },
@@ -17106,8 +17104,8 @@ Etiquette — WHEN to act (the judgment; per-command mechanics are listed below)
     the recall snippet AND sharpens recall (it's embedded with the body).
   · 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.
+  · Respond to requests THROUGH them — \`arbor respond\` (or \`arbor stamp\` a review request) so the
+    request completes and the requester is notified; a plain reply that skips \`respond\` leaves it 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.

package/package.json

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