@lambdacurry/arbor 0.7.1 → 0.8.1

package/dist/arbor.js

@@ -1652,6 +1652,17 @@ var notificationCursors = sqliteTable("notification_cursors", {
   profileId: text("profile_id").primaryKey().references(() => profiles.id),
   lastSeenAt: ts("last_seen_at").notNull()
 });
+var watches = sqliteTable("watches", {
+  id: text("id").primaryKey(),
+  watcherProfileId: text("watcher_profile_id").notNull().references(() => profiles.id),
+  targetType: text("target_type").$type().notNull(),
+  targetId: text("target_id").notNull(),
+  cadence: text("cadence").$type().notNull().default("digest"),
+  createdAt: ts("created_at").notNull()
+}, (t) => ({
+  watchUq: uniqueIndex("watches_watcher_target_uniq").on(t.watcherProfileId, t.targetType, t.targetId),
+  watchTargetIdx: index("watches_target_idx").on(t.targetType, t.targetId)
+}));
 // ../core/src/ops/onboarding.ts
 var INVITE_TTL_MS = 7 * 24 * 60 * 60 * 1000;
 var EMOJI_RE = new RegExp("^\\p{RGI_Emoji}$", "v");
@@ -16033,7 +16044,7 @@ config(en_default());
 var ORIENTATION = `Arbor is your team's deliberation room and shared memory — people and agents settle typed work here, and Arbor remembers what's decided. To work well:
 
 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. 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. 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.
-2. CONTRIBUTE typed points — ONE point per contribution, 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: one typed point is reviewable on its own, and 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.
+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).
 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.
@@ -16079,7 +16090,7 @@ var ACTIONS = [
   {
     name: "contribute",
     title: "Contribute to a thread",
-    description: "Add your own typed contribution (proposal/critique/question/evidence/…) — ONE point per contribution, on the record. RECALL FIRST (recalling beats re-deriving), and put references IN THE BODY: URLs and inline [label](#con_…) refs become typed reference edges + smart pills automatically. Body refs are CITATIONS (AD-196) — they never change where your contribution sits in the thread, so cite freely. To thread your contribution UNDER a specific one (a reply), pass links: [{rel: 'inReplyTo', targetId}] — that deliberate edge is what nests it.",
+    description: "Add your own typed contribution (proposal/critique/question/evidence/…) — ONE point per contribution, on the record. BEFORE ADDING, ask what the most additive move is — not just whether to say something (AD-205): if your reaction to a point already on the record fits in one line — agree OR disagree — STAMP it (vouch, or push back with your one-line why), don't restate it as a contribution; contribute what's genuinely NEW (a typed move — a developed critique counts — that advances THIS thread's objective); if you'd only be echoing, reviewing IS the contribution and staying out is fine. RECALL FIRST (recalling beats re-deriving), and put references IN THE BODY: URLs and inline [label](#con_…) refs become typed reference edges + smart pills automatically. Body refs are CITATIONS (AD-196) — they never change where your contribution sits in the thread, so cite freely. An artifact ref ([label](#art_…)) on its OWN LINE unfurls into a preview CARD (a peek of the doc/table); inline in a sentence it stays a compact pill (AD-204) — so put an artifact on its own line when you want the reader to SEE it. To thread your contribution UNDER a specific one (a reply), pass links: [{rel: 'inReplyTo', targetId}] — that deliberate edge is what nests it.",
     inputSchema: {
       threadId: exports_external.string().describe("the thread id, e.g. thr_…"),
       type: exports_external.enum(CONTRIBUTION_TYPES).describe("the contribution type (AD-066 taxonomy)"),
@@ -16100,7 +16111,7 @@ var ACTIONS = [
   {
     name: "edit",
     title: "Edit your contribution",
-    description: "Edit the BODY of your own contribution (AD-132 — editable-but-audited: the displayed text changes, an 'edited' marker appears, and the event log keeps the previous body). Author-only; the type and DELIBERATE links (reply edges, fulfills) are fixed — body-borne prose refs follow the edited body: a [label](#con_…) you edit in gains its citation edge, one you edit out drops it (AD-196). A different point is a NEW contribution, not an edit.",
+    description: "Edit the BODY of your own contribution (AD-132 — editable-but-audited: the displayed text changes, an 'edited' marker appears, and the event log keeps the previous body). Author-only; the type and DELIBERATE links (reply edges, fulfills) are fixed — body-borne prose refs follow the edited body: a [label](#con_…) you edit in gains its citation edge, one you edit out drops it (AD-196). An artifact ref ([label](#art_…)) on its OWN LINE renders as a preview card; inline it stays a pill (AD-204). A different point is a NEW contribution, not an edit.",
     inputSchema: {
       contributionId: exports_external.string().describe("your contribution's id, con_…"),
       body: exports_external.string().min(1).describe("the replacement markdown body"),
@@ -16876,6 +16887,59 @@ var ACTIONS = [
       read_all: "notification.markAllRead"
     })
   },
+  {
+    name: "watch",
+    title: "Watch for changes",
+    description: "CHOSEN attention (AD-202) — subscribe to a thread/artifact/topic and get a notification when it changes, even on work you didn't touch (participation already notifies you about threads you're in; watch is for the rest). verb=on: start watching (targetType thread|artifact|topic + targetId). verb=off: stop. verb=status: are you watching this one? verb=list: everything you watch. A watched thread pings on a new contribution, an artifact on a new version, a topic on a new thread — bursts collapse into one row, so watching a busy target is safe. Watching is PRIVATE (nobody sees you watch).",
+    inputSchema: {
+      verb: exports_external.enum(["on", "off", "status", "list"]).describe("start/stop/check watching, or list"),
+      targetType: exports_external.enum(["thread", "artifact", "topic"]).optional().describe("on/off/status: what to watch"),
+      targetId: exports_external.string().optional().describe("on/off/status: the id (thr_/art_/top_)"),
+      cadence: exports_external.enum(["immediate", "digest"]).optional().describe("on: email cadence for later (stored now; in-app fires regardless today)")
+    },
+    surfaces: ["mcp"],
+    toolset: "loop",
+    run: dispatch({
+      on: "watch.toggle",
+      off: "watch.toggle",
+      status: "watch.get",
+      list: "watch.list"
+    }, (verb, input) => verb === "off" ? { ...input, watching: false } : input)
+  },
+  {
+    name: "watch_target",
+    title: "Watch a thread/artifact/topic",
+    description: "Start watching a thread, artifact, or topic (AD-202) — you'll be notified on its next change (new contribution / version / thread) even if you never touched it. Private; bursts collapse to one notification.",
+    inputSchema: {
+      targetType: exports_external.enum(["thread", "artifact", "topic"]).describe("what to watch"),
+      targetId: exports_external.string().describe("the id (thr_/art_/top_)"),
+      cadence: exports_external.enum(["immediate", "digest"]).optional().describe("email cadence for later (in-app fires regardless today)")
+    },
+    surfaces: ["cli"],
+    toolset: "loop",
+    run: forward("watch.toggle")
+  },
+  {
+    name: "unwatch_target",
+    title: "Stop watching",
+    description: "Stop watching a thread/artifact/topic (AD-202). Idempotent.",
+    inputSchema: {
+      targetType: exports_external.enum(["thread", "artifact", "topic"]).describe("what to stop watching"),
+      targetId: exports_external.string().describe("the id (thr_/art_/top_)")
+    },
+    surfaces: ["cli"],
+    toolset: "loop",
+    run: (ex, input) => ex.call("watch.toggle", { ...input, watching: false })
+  },
+  {
+    name: "watches",
+    title: "List what you watch",
+    description: "List every thread/artifact/topic you're watching (AD-202), newest first.",
+    inputSchema: {},
+    surfaces: ["cli"],
+    toolset: "loop",
+    run: forward("watch.list")
+  },
   {
     name: "curation",
     title: "Curate the record",

package/package.json

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