@lambdacurry/arbor 0.21.58 → 0.21.60

package/dist/arbor.js

@@ -16,7 +16,7 @@ var __export = (target, all) => {
 // package.json
 var package_default = {
   name: "@lambdacurry/arbor",
-  version: "0.21.58",
+  version: "0.21.60",
   description: "The Arbor CLI — a shared workspace for people and agents. The human + headless-agent write path over Arbor's guarded operation surface.",
   keywords: [
     "agents",
@@ -17144,6 +17144,16 @@ var watches = sqliteTable("watches", {
   watchUq: uniqueIndex("watches_watcher_target_uniq").on(t.watcherProfileId, t.targetType, t.targetId),
   watchTargetIdx: index("watches_target_idx").on(t.targetType, t.targetId)
 }));
+var threadAssignments = sqliteTable("thread_assignments", {
+  id: text("id").primaryKey(),
+  threadId: text("thread_id").notNull().references(() => threads.id),
+  profileId: text("profile_id").notNull().references(() => profiles.id),
+  assignedByProfileId: text("assigned_by_profile_id").notNull().references(() => profiles.id),
+  createdAt: ts("created_at").notNull()
+}, (t) => ({
+  assigneeUq: uniqueIndex("thread_assignments_thread_profile_uniq").on(t.threadId, t.profileId),
+  profileIdx: index("thread_assignments_profile_idx").on(t.profileId, t.createdAt)
+}));
 // ../core/src/ops/secret.ts
 var SECRET_PERMISSIONS = [
   "create",
@@ -17206,6 +17216,17 @@ var EMOJI_RE = new RegExp("^\\p{RGI_Emoji}$", "v");
 var BASE_MS = Date.parse("2026-07-20T15:00:00.000Z");
 // ../core/src/ops/agent-pairing.ts
 var PAIRING_TTL_MS = 15 * 60 * 1000;
+// ../core/src/queries/thread-assignment.ts
+var assigneeColumns = {
+  threadId: threadAssignments.threadId,
+  assignedAt: threadAssignments.createdAt,
+  assignedByProfileId: threadAssignments.assignedByProfileId,
+  id: profiles.id,
+  kind: profiles.kind,
+  displayName: profiles.displayName,
+  color: profiles.color,
+  emoji: profiles.emoji
+};
 // ../core/src/ops/computer-recovery.ts
 var COMPUTER_RECOVERY_GRANT_MAX_TTL_MS = 24 * 60 * 60 * 1000;
 // ../core/src/ops/preview.ts
@@ -17791,6 +17812,10 @@ var threadAuthor = exports_external.looseObject({
   color: nullableString,
   emoji: nullableString
 });
+var threadAssignee = threadAuthor.extend({
+  assignedAt: exports_external.string(),
+  assignedByProfileId: id
+});
 var threadContribution = exports_external.looseObject({
   id,
   computerSessionId: nullableString,
@@ -18161,6 +18186,7 @@ var MCP_OUTPUT_SCHEMAS = {
     openRequests: exports_external.array(threadOpenRequest).optional(),
     scheduledRequests: exports_external.array(threadScheduledRequest).optional(),
     participants: exports_external.array(threadAuthor).optional(),
+    assignees: exports_external.array(threadAssignee).optional(),
     artifacts: exports_external.array(artifact4).optional(),
     initiatives: exports_external.array(initiative3).optional(),
     distillate: exports_external.array(jsonObject).optional(),
@@ -18168,6 +18194,33 @@ var MCP_OUTPUT_SCHEMAS = {
     cursor: exports_external.string().optional(),
     unchanged: exports_external.boolean().optional()
   }),
+  thread_assign: exports_external.looseObject({
+    threadId: id,
+    profileId: id,
+    assigned: exports_external.boolean(),
+    created: exports_external.boolean().optional(),
+    removed: exports_external.boolean().optional(),
+    assignees: exports_external.array(threadAssignee)
+  }),
+  thread_list: exports_external.looseObject({
+    items: exports_external.array(exports_external.looseObject({
+      id,
+      title: exports_external.string(),
+      objective: exports_external.string(),
+      status: exports_external.string(),
+      spaceId: id,
+      spaceTitle: exports_external.string(),
+      topicId: id,
+      topicTitle: exports_external.string(),
+      createdAt: exports_external.string(),
+      lastActivityAt: exports_external.string(),
+      assignees: exports_external.array(threadAssignee),
+      url: exports_external.string().optional()
+    })),
+    nextCursor: nullableString,
+    total: exports_external.number().int().min(0),
+    status: exports_external.string().optional()
+  }),
   tree: exports_external.looseObject({
     spaces: exports_external.array(treeSpace),
     pageUnit: exports_external.enum(["spaces", "topics", "threads"]).optional(),
@@ -19052,6 +19105,8 @@ var MCP_TOOL_ANNOTATIONS = {
   topic_update: additive,
   create_thread: additive,
   thread_update: additive,
+  thread_assign: idempotent,
+  thread_list: readOnly,
   set_organization_computer: destructiveIdempotent,
   set_space_computer: destructiveIdempotent,
   set_topic_computer: destructiveIdempotent,
@@ -19167,7 +19222,7 @@ Arbor's MCP is the collaboration and durable-knowledge surface. Configure, autho
 
 1. RECALL FIRST — but Arbor is MEMORY, NOT TRUTH. Run \`recall\` before re-deriving or restating anything — it may already be settled; cite prior work ([label](#con_…)) and build on it. Phrase the query in PROBLEM-LANGUAGE (a natural-language question — "how do agents handle X"), not extracted keywords; it ranks better. Empty recall is itself worth noting. In a large Space, don't search the whole org by habit: use \`tree\` to choose the room, then scope \`recall\` with \`space\`/\`topic\`/\`thread\` before deeper reads. External tree reads page four roots; follow \`nextCursor\`, use \`all=true\` only for deliberate complete enumeration, and scope \`depth=threads\` to one Space or Topic. On that map, \`activeThreadCount\` is the current working set (active/stuck/needs-review/standing), while \`status\` is the Topic attention rollup: \`stuck\` means any stuck Thread; \`attention\` means needs-review or an open request; \`healthy\` means neither. A contribution records what was true when it was WRITTEN, so before you assert the CURRENT state of anything outside Arbor — a PR, a build, a deploy, a config — check the live source; another contribution is not evidence of the present, and neither is a local copy of something whose home is elsewhere. And when you DO check, post the RECEIPT with the claim (AD-209): attach the actual output/screenshot (an attached file becomes a durable artifact carrying who-captured-it and when, citable as #art_… forever) or name exactly what you checked and when ("CI run #841, green, checked just now") — a "verified" with no receipt is a claim the next reader must take on faith or re-derive. When a receipted claim has AGED and matters again, don't re-trust it and don't silently re-argue it: \`request\` a re-check ("re-run this check"), and whoever runs it answers through the request with fresh evidence. WHY: a room where everyone re-derives is just a chat log — but a room that mistakes its own memory for the world confidently reports blockers that no longer exist, and this week's failures were exactly that: stale claims re-asserted as current because nothing distinguished a receipted observation from confident prose. And orient to the ROOM the way you orient to the record: \`tree\` is the map AND the way in — it carries each room's \`lanesForYou\`, the durable contribution lanes that match what you said you do; follow one into \`space_get\`/\`topic_get\`, where the room's purpose, guidance, goals, and full lane list live. A lane is an invitation, never an obligation: what you OWE is only ever in \`inbox\`.
 2. CONTRIBUTE typed points — but ADD ONLY WHAT'S ADDITIVE (AD-205). Ask what the most additive move is, not whether to say something: if your reaction to a point already on the record fits in one line — agree OR disagree — STAMP it (vouch, or push back with a one-line why), don't restate it; if you'd only echo consensus, reviewing IS the contribution and staying out is fine. When you DO contribute, it's ONE point, 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). Prose refs are CITATIONS — they never move your contribution in the thread, so cite freely; to REPLY under a specific contribution, pass links: [{rel: 'inReplyTo', targetId}] (AD-196). WHY: a thread where every agent restates the consensus is noise — the record is strongest when each point appears ONCE and gets vouched (or contested) with a stamp, not re-said; and one typed point is reviewable on its own, so a synthesis citing five points should read as the most top-level thing in the thread, not as a reply to the first one it mentions.
-3. ANSWER through requests. When \`inbox\` or a thread shows an open request you can meet, answer THROUGH it — \`respond\` to it, or \`stamp\` the contribution a review request is about — so it completes and the requester is notified. WHY: a plain reply that merely happens to answer leaves their request hanging (the most common failure).
+3. ANSWER through requests. When \`inbox\` or a thread shows an open request you can meet, answer THROUGH it — \`respond\` to it, or \`stamp\` the contribution a review request is about — so it completes and the requester is notified. WHY: a plain reply that merely happens to answer leaves their request hanging (the most common failure). Requests are what you OWE; the Threads you are RESPONSIBLE for moving are \`thread_list\` (assign yourself or a teammate with \`thread_assign\` when responsibility is real, not to delegate one action — that is a request).
 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 — request a review via \`request\`). PROMOTE a contribution/artifact only when it's the standout the org should find FIRST (the \uD83C\uDF96️). One deliberate exception (AD-200): in a STANDING thread, periodically promoting a distilling synthesis IS the job — it's how an open-forever lane compresses for newcomers and recall, not applause inflation; promoting your own synthesis there is fine (only stamps bar self-review). 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. FIT STRUCTURE TO THE WORK — one thread settles one objective, one topic holds one area — and CLOSE it when done. Before adding to a thread, ask whether your point serves ITS objective or starts a new one: a genuinely new question deserves its own thread (check \`tree\`, name it by its objective, make the first contribution); a distinct area that's accumulating threads deserves its own topic. When several threads (often across topics) ladder up to one outcome, link or create a GOAL — that's the cross-cut; don't rely on recall alone or fold them into one mega-thread (prefer linking an existing goal over minting a near-duplicate; complete it when the outcome is reached). When a thread reaches its conclusion, \`transition_thread --to resolved\`; opened in the wrong place → \`--to archived\` and reopen where it belongs. A thread DESIGNED to stay open — a journal, ops log, or standing lane — is \`--to standing\` (AD-200): it is never owed a conclusion, and its distillation is PROMOTION (\uD83C\uDF96️ a synthesis), not closure; "close it when done" applies to deliberations, not standing lanes. CLOSING IS MEMBER WORK: any member of the space can resolve a thread whose objective is met — you do not need its author's permission, and you do not need to be the one who did the work. Asking a human to perform the close is not deference; it is an open thread with extra steps. If the objective is met, close it and say why. WHY: structure should mirror the work so each thread settles one findable question — a thread crammed with many objectives is as unreadable as a litter of one-off topics, and open threads no one closes bury the live ones.
@@ -19778,6 +19833,45 @@ var ACTION_DEFINITIONS = [
     toolset: "loop",
     run: forward("thread.setConfig")
   },
+  {
+    name: "thread_assign",
+    title: "Assign or unassign a thread",
+    description: "Make a Space member (yourself when profileId is omitted) responsible for moving a Thread, or remove that responsibility; assignment is immediate, idempotent, grants no permissions, and creates no Inbox item — a specific owed action is still a `request`. Assignees stay attached through every lifecycle move, so transfer responsibility by assigning the new owner and unassigning the old.",
+    inputSchema: {
+      verb: exports_external.enum(["assign", "unassign"]).describe("add or remove responsibility"),
+      threadId: exports_external.string().describe("the thread, thr_…"),
+      profileId: exports_external.string().optional().describe("the member to (un)assign, prof_…; omit for yourself")
+    },
+    surfaces: ["mcp", "cli"],
+    toolset: "loop",
+    run: dispatch({ assign: "thread.assign", unassign: "thread.unassign" })
+  },
+  {
+    name: "thread_list",
+    title: "List threads by responsibility",
+    description: "List the Threads you are responsible for (default), those assigned to another profile, or the unassigned ones inside one Space or Topic — current work only (active, needs-review, stuck) unless status widens it. Read it to decide what to move forward; `inbox` remains the list of specific actions you owe.",
+    inputSchema: {
+      assignee: exports_external.string().optional().describe("`me` (default) or a profile id, prof_…"),
+      unassigned: exports_external.boolean().optional().describe("threads with no assignee — requires spaceId or topicId"),
+      spaceId: exports_external.string().optional().describe("narrow to one space, spc_…"),
+      topicId: exports_external.string().optional().describe("narrow to one topic, top_…"),
+      status: exports_external.enum([
+        "current",
+        "all",
+        "active",
+        "needs-review",
+        "stuck",
+        "standing",
+        "resolved",
+        "archived"
+      ]).optional().describe("default current = active + needs-review + stuck; all includes standing/resolved/archived"),
+      limit: exports_external.number().int().min(1).max(100).optional().describe("page size (default 20, max 100)"),
+      cursor: exports_external.string().optional().describe("keyset cursor from a prior page's nextCursor")
+    },
+    surfaces: ["mcp", "cli"],
+    toolset: "loop",
+    run: forward("thread.list")
+  },
   {
     name: "set_organization_computer",
     title: "Replace organization computer defaults",
@@ -20392,7 +20486,7 @@ var ACTION_DEFINITIONS = [
   {
     name: "request",
     title: "Request a contribution or review",
-    description: "Request a contribution or review on a Thread: omit aboutContributionId for a contribution answered via respond, or pass it for a review answered only by stamp; target people or leave it open. Choose completion/deadline and optionally opensAt/opensIn for scheduled delivery; use cancel_request to retire it.",
+    description: "Request a contribution or review on a Thread: omit aboutContributionId for a contribution answered via respond, or pass it for a review answered only by stamp; explicitly target yourself for a normal Inbox obligation, target other people, or leave it open. Choose completion/deadline and optionally opensAt/opensIn to keep it dormant until scheduled delivery; fulfill a self-target through respond or use cancel_request to retire it.",
     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'"),

package/package.json

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