@lambdacurry/arbor 0.23.24 → 0.23.26

package/dist/arbor.js

@@ -2,7 +2,7 @@
 // package.json
 var package_default = {
   name: "@lambdacurry/arbor",
-  version: "0.23.24",
+  version: "0.23.26",
   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",
@@ -7967,6 +7967,22 @@ var ORG_ADMIN_CONTAINMENT_PERMISSIONS = new Set([
   "revoke"
 ]);
 
+// ../core/src/ops/space.ts
+var GUIDANCE_LIMITS = {
+  maxItems: 12,
+  maxItemLength: 500
+};
+var MAX_GUIDANCE = GUIDANCE_LIMITS.maxItems;
+var MAX_GUIDANCE_LEN = GUIDANCE_LIMITS.maxItemLength;
+var CONTRIBUTION_LANE_LIMITS = { maxItems: 6, maxItemLength: 120 };
+var MAX_LANES = CONTRIBUTION_LANE_LIMITS.maxItems;
+var MAX_LANE_LEN = CONTRIBUTION_LANE_LIMITS.maxItemLength;
+
+// ../core/src/ops/thread.ts
+var WAYS_TO_HELP_LIMITS = { maxItems: 12, maxItemLength: 200 };
+var MAX_WAYS = WAYS_TO_HELP_LIMITS.maxItems;
+var MAX_WAY_LEN = WAYS_TO_HELP_LIMITS.maxItemLength;
+
 // ../core/src/ops/computer-output.ts
 var COMPUTER_OUTPUT_DEFAULT_STALE_MS = 24 * 60 * 60 * 1000;
 
@@ -8063,6 +8079,12 @@ var TASK_CACHE_FINAL_TTL_MS = 7 * 24 * 60 * 60 * 1000;
 var TASK_CACHE_RECOVERABLE_TTL_MS = 30 * 24 * 60 * 60 * 1000;
 // ../core/src/ops/computer-recovery.ts
 var COMPUTER_RECOVERY_GRANT_MAX_TTL_MS = 24 * 60 * 60 * 1000;
+// ../core/src/ops/computer-retention.ts
+var snapshotColumns = {
+  id: computerSnapshots.id,
+  provider: computerSnapshots.provider,
+  providerRef: computerSnapshots.providerRef
+};
 // ../core/src/ops/preview.ts
 var PREVIEW_ENTRY_MIME = "text/html; charset=utf-8";
 var PREVIEW_MAX_BYTES = 2 * 1024 * 1024;
@@ -10768,7 +10790,7 @@ var ORIENTATION_SECTIONS = [
   },
   {
     brief: "1. Recall before re-deriving, but Arbor is memory, not truth: check live sources and post what you checked.",
-    full: `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\`.`
+    full: `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 room's standing ways to help (\`contributionLanes\`) that match what you said you do; follow one into \`space_get\`/\`topic_get\`, where the room's purpose, guidance, goals, and full list of ways to help live. A way to help is an invitation, never an obligation: what you OWE is only ever in \`inbox\`.`
   },
   {
     brief: "2. Contribute one additive, typed point a newcomer can follow; stamp instead of restating.",
@@ -11376,7 +11398,7 @@ var ACTION_DEFINITIONS = [
   {
     name: "topic_update",
     title: "Edit a topic's title or purpose",
-    description: "Edit a Topic's title or purpose facts, or select `--workflow` from `space_get.workflows` by summary (unattached ids are rejected; blank inherits the Space default), patching only supplied fields. Use this to correct stale area metadata; norms belong in topic guidance and lanes instead.",
+    description: "Edit a Topic's title or purpose facts, or select `--workflow` from `space_get.workflows` by summary (unattached ids are rejected; blank inherits the Space default), patching only supplied fields. Use this to correct stale area metadata; norms belong in topic guidance and ways to help instead.",
     inputSchema: {
       topicId: string2().describe("the topic to edit, top_…"),
       title: string2().min(1).optional().describe("a new title — an area of work, not a question"),
@@ -11413,11 +11435,11 @@ var ACTION_DEFINITIONS = [
   },
   {
     name: "set_space_lanes",
-    title: "Set a space's contribution lanes",
-    description: "Set a SPACE's DURABLE contribution lanes (AD-222) — the standing kinds of help this room wants, as short matchable labels ('security review', 'cold-start performance', 'onboarding copy'). This is the discovery surface: a member whose capabilities/charter share a word with a lane sees it quoted in their `tree` as `lanesForYou`, and reads the full list via `space_get`. Distinct from `set_space_guidance` (HOW we work here) and from a thread's ways-to-help (a temporary, thread-local ask). At most 6 lanes, 120 characters each — over the cap is rejected, never truncated. Replaces the whole list; pass [] to clear.",
+    title: "Set a space's ways to help",
+    description: "Set a SPACE's standing ways to help (`contributionLanes`, AD-222) — the kinds of help this room wants, as short matchable labels ('security review', 'cold-start performance', 'onboarding copy'); people see them as \"Ways to help\" on the Space. This is the discovery surface: a member whose capabilities/charter share a word with one sees it quoted in their `tree` as `lanesForYou`, and reads the full list via `space_get`. Distinct from `set_space_guidance` (HOW we work here) and from a thread's `waysToHelp` (a temporary, thread-local ask). At most 6 items, 120 characters each — over the cap is rejected, never truncated. Replaces the whole list; pass [] to clear.",
     inputSchema: {
       spaceId: string2().describe("the space, spc_…"),
-      contributionLanes: proseList("the full lane list — replaces the existing one; [] clears it")
+      contributionLanes: proseList("the full list of ways to help — replaces the existing one; [] clears it")
     },
     surfaces: ["cli"],
     toolset: "spaces",
@@ -11425,11 +11447,11 @@ var ACTION_DEFINITIONS = [
   },
   {
     name: "set_topic_lanes",
-    title: "Set a topic's contribution lanes",
-    description: "Set a TOPIC's DURABLE contribution lanes (AD-222) — the same axis as `set_space_lanes`, narrowed to one area of work. Read back in full via `topic_get`; matched (at most two, verbatim) into `tree`. At most 6 lanes, 120 characters each — over the cap is rejected, never truncated. Replaces the whole list; pass [] to clear.",
+    title: "Set a topic's ways to help",
+    description: "Set a TOPIC's standing ways to help (`contributionLanes`, AD-222) — the same axis as `set_space_lanes`, narrowed to one area of work. Read back in full via `topic_get`; matched (at most two, verbatim) into `tree` as `lanesForYou`. At most 6 items, 120 characters each — over the cap is rejected, never truncated. Replaces the whole list; pass [] to clear.",
     inputSchema: {
       topicId: string2().describe("the topic, top_…"),
-      contributionLanes: proseList("the full lane list — replaces the existing one; [] clears it")
+      contributionLanes: proseList("the full list of ways to help — replaces the existing one; [] clears it")
     },
     surfaces: ["cli"],
     toolset: "spaces",
@@ -11996,7 +12018,7 @@ var ACTION_DEFINITIONS = [
   {
     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 orienting someone on how they could pitch in with THIS thread as it stands (e.g. 'a benchmark on cold-start latency'). It is thread-local and temporary: it is read inside `thread_get`, and it never rolls up into a space/topic orientation surface — a standing statement about what a room wants is a contribution LANE (`set_space_lanes`/`set_topic_lanes`, AD-222). Guidance you READ, NOT an obligation — that's `request`. Replaces the whole list; pass [] to clear.",
+    description: "Set a thread's READ-ONLY 'ways to help' (AD-038) — a short, curated list of perspectives, skills, or concrete tasks orienting someone on how they could pitch in with THIS thread as it stands (e.g. 'a benchmark on cold-start latency'). It is thread-local and temporary: it is read inside `thread_get`, and it never rolls up into a space/topic orientation surface — a standing statement about what a room wants is the room's standing ways to help (`contributionLanes`, via `set_space_lanes`/`set_topic_lanes`, AD-222). Guidance you READ, NOT an obligation — that's `request`. Replaces the whole list; pass [] to clear.",
     inputSchema: {
       threadId: string2().describe("the thread, thr_…"),
       waysToHelp: proseList("the full ways-to-help list — replaces the existing one; [] clears it")
@@ -12754,7 +12776,7 @@ var ACTION_DEFINITIONS = [
   {
     name: "space_get",
     title: "Read a space",
-    description: "Read a Space's durable context—purpose, guidance, contribution lanes, attached workflows with summaries, Topics—and a paged member roster with roles, capabilities, and charters (default 50; `total` is the full roster size). Continue with `cursor`, or use `all=true` / `--all` only when you need every member; it cannot modify membership or guidance.",
+    description: "Read a Space's durable context—purpose, guidance, the room's standing ways to help (`contributionLanes`), attached workflows with summaries, Topics—and a paged member roster with roles, capabilities, and charters (default 50; `total` is the full roster size). Continue with `cursor`, or use `all=true` / `--all` only when you need every member; it cannot modify membership or guidance.",
     inputSchema: {
       spaceId: string2().min(1).describe("the space id"),
       ...PAGINATION_INPUT
@@ -12766,7 +12788,7 @@ var ACTION_DEFINITIONS = [
   {
     name: "topic_get",
     title: "Read a topic",
-    description: "Read a Topic's durable context, guidance, selected workflow summary, open requests, promoted artifacts, and a paged Thread roster (default 50; `total` is the full roster size). Continue with `cursor`, or use `all=true` / `--all` only for intentional complete enumeration; for a concrete question in a large Topic, prefer Topic-scoped `recall`.",
+    description: "Read a Topic's durable context, guidance, the room's standing ways to help (`contributionLanes`), selected workflow summary, open requests, promoted artifacts, and a paged Thread roster (default 50; `total` is the full roster size). Continue with `cursor`, or use `all=true` / `--all` only for intentional complete enumeration; for a concrete question in a large Topic, prefer Topic-scoped `recall`.",
     inputSchema: {
       topicId: string2().min(1).describe("the topic id"),
       ...PAGINATION_INPUT
@@ -13717,7 +13739,7 @@ var ACTION_DEFINITIONS = [
   {
     name: "charter",
     title: "Set the guidance surfaces",
-    description: "Write collaboration guidance: space_charter for a member's per-Space operating charter, space/topic guidance for durable how-we-work-here norms, space/topic lanes for the durable kinds of help welcome there, or ways_to_help for one Thread's temporary needs. Each write replaces the selected value/list (empty clears).",
+    description: "Write collaboration guidance: space_charter for a member's per-Space operating charter, space/topic guidance for durable how-we-work-here norms, space_lanes/topic_lanes for the room's standing ways to help (`contributionLanes`), or ways_to_help for one Thread's temporary needs. Each write replaces the selected value/list (empty clears).",
     inputSchema: {
       verb: _enum([
         "space_charter",
@@ -13732,7 +13754,7 @@ var ACTION_DEFINITIONS = [
       profileId: string2().optional().describe("space_charter admin override: whose charter"),
       topicId: string2().optional().describe("topic_guidance/topic_lanes: the topic, top_…"),
       guidance: proseList("space_guidance/topic_guidance: full list, replaces; [] clears").optional(),
-      contributionLanes: proseList("space_lanes/topic_lanes: full lane list, replaces; [] clears").optional(),
+      contributionLanes: proseList("space_lanes/topic_lanes: full list of ways to help, replaces; [] clears").optional(),
       threadId: string2().optional().describe("ways_to_help: the thread, thr_…"),
       waysToHelp: proseList("ways_to_help: full list, replaces; [] clears").optional()
     },

package/package.json

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