@lambdacurry/arbor 0.24.32 → 0.24.33

package/dist/arbor.js

@@ -11273,6 +11273,21 @@ function buildOutputSchemas() {
     lanesForYou: array(string2()).optional(),
     topics: array(treeTopic).optional()
   });
+  const quickSearchResult = looseObject({
+    exact: looseObject({
+      id,
+      kind: string2(),
+      title: string2(),
+      href: string2(),
+      score: number2()
+    }).nullable().optional(),
+    groups: array(looseObject({
+      kind: string2(),
+      band: string2(),
+      hits: array(jsonObject),
+      more: literal(true).optional()
+    }))
+  });
   const paged = (key, item) => looseObject({
     [key]: array(item),
     total: number2().optional(),
@@ -11620,8 +11635,10 @@ function buildOutputSchemas() {
       spaces: array(treeSpace),
       pageUnit: _enum(["spaces", "topics", "threads"]).optional(),
       total: number2().int().min(0).optional(),
-      nextCursor: string2().optional()
+      nextCursor: string2().optional(),
+      matches: quickSearchResult.optional()
     }),
+    quick_search: quickSearchResult,
     members: looseObject({
       members: array(orgMember),
       total: number2().optional(),
@@ -13080,6 +13097,7 @@ var MCP_TOOL_ANNOTATIONS = {
   org_leave: destructive,
   introduce: additive,
   thread_get: readOnly,
+  quick_search: readOnly,
   tree: readOnly,
   members: readOnly,
   space_create: additive,
@@ -13451,7 +13469,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 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\`.`
+    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. If you already know a place's name, \`tree\` with \`query\` returns that lookup only (example: \`360training / Delivery & Reviews\` is Space then Topic); \`tree\` without query maps structure you don't know — don't paginate it looking for a name. In a large Space, don't search the whole org by habit: 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.",
@@ -15328,11 +15346,12 @@ var ACTION_DEFINITIONS = [
   {
     name: "quick_search",
     title: "Quick search places",
-    description: "Jump to a place or person by name or short id: the Spaces, Topics, Threads and Artifacts you can open whose title (or objective, purpose, summary) contains every word, the people in your org whose name matches, best name match first, and an exact Thread short id (BUD-34) as `exact`. With `content`, the contributions you can open whose text holds every word (whole words, any word form), best match first, each with a short quote. The web ⌘K palette's two lookups: lexical, no embedding, no scope. To search what was said by meaning, use `recall`.",
+    description: "Jump to a place or person by name or short id: the Spaces, Topics, Threads and Artifacts you can open whose title (or objective, purpose, summary) contains every word, the people in your org whose name matches, best name match first, and an exact Thread short id (BUD-34) as `exact`. With `content`, the contributions you can open whose text holds every word (whole words, any word form), best match first, each with a short quote. The web ⌘K palette's two lookups: lexical, no embedding, no scope. Named navigation is `tree` with `query`; meaning is `recall`.",
     inputSchema: {
       q: string2().min(2).max(200).describe("a place or person name to look up, or a Thread short id such as BUD-34"),
       content: boolean2().optional().describe("search what contributions said instead of place names")
     },
+    cliHelpLead: "Unscoped name lookup (palette parity). Named navigation → `arbor tree --query`. Content by meaning → `arbor recall`.",
     surfaces: ["cli"],
     toolset: "loop",
     run: Object.assign((ex, { content, ...input }) => ex.call(content === true ? "search.content" : "search.quick", input), { operations: ["search.quick", "search.content"] })
@@ -15340,8 +15359,9 @@ var ACTION_DEFINITIONS = [
   {
     name: "tree",
     title: "Navigate the workspace tree",
-    description: `Map Spaces to Topics to Threads for orientation; external reads page ${TREE_EXTERNAL_DEFAULT_PAGE_SIZE} roots by default, while all=true is explicit complete retrieval: unscoped tree pages Spaces, Space-scoped tree pages Topics, and Topic-scoped depth=threads pages Threads. For a bounded Thread roster, scope to one Topic; Topic activeThreadCount is the current working set, status is area attention, not personal obligation (inbox), and depth=threads should stay scoped unless complete enumeration is intentional.`,
+    description: `Map Spaces to Topics to Threads; query matches only (\`360training / Delivery & Reviews\`); external reads page ${TREE_EXTERNAL_DEFAULT_PAGE_SIZE} roots by default, all=true is complete: unscoped tree pages Spaces, Space-scoped tree pages Topics, and Topic-scoped depth=threads pages Threads. For a bounded Thread roster, scope to one Topic; Topic activeThreadCount is the current working set, status is area attention, not personal obligation (inbox), and depth=threads should stay scoped unless complete enumeration is intentional.`,
     inputSchema: {
+      query: string2().min(2).max(200).optional().describe('known name or slash path ("360training / Delivery & Reviews"); returns matches only (no map/page); space/topic ids still scope the lookup'),
       space: string2().optional().describe("scope to one space id (spc_…)"),
       topic: string2().optional().describe("scope to one topic id (top_…)"),
       depth: _enum(["spaces", "topics", "threads"]).optional().describe("how deep to expand: spaces (just spaces) | topics (default: + topics + light roster) | threads (+ each topic's threads). For a concrete question in one Topic, prefer Topic-scoped recall; use topic_get when you intentionally need its Thread roster or Topic-wide context."),
@@ -15349,6 +15369,7 @@ var ACTION_DEFINITIONS = [
       cursor: PAGINATION_INPUT.cursor,
       all: PAGINATION_INPUT.all
     },
+    cliHelpLead: 'Known name → `arbor tree --query "360training / Delivery & Reviews"`. Map structure → `arbor tree`. Content by meaning → `arbor recall`.',
     externalReadDefaults: { limit: TREE_EXTERNAL_DEFAULT_PAGE_SIZE },
     surfaces: ["mcp", "cli"],
     toolset: "loop",
@@ -16767,7 +16788,7 @@ var ACTIONS = ACTION_DEFINITIONS.map((action) => {
 });
 
 // ../actions/src/retention-entry.ts
-var ARBOR_VERSION = "0.24.32";
+var ARBOR_VERSION = "0.24.33";
 var historyPolicySchema = _enum(["full", "checkpoint"]).optional().describe("text Artifacts: future history retention policy; full retains every source snapshot, checkpoint keeps metadata for every revision and source only when explicitly retained");
 var retainSourceSchema = boolean2().optional().describe("edit: in checkpoint mode, retain this newly minted content revision's source");
 var checkpointSchema = boolean2().optional().describe("edit: retain the exact current version source without incrementing content version");
@@ -17175,7 +17196,7 @@ function dispositionFilename(value) {
 // package.json
 var package_default = {
   name: "@lambdacurry/arbor",
-  version: "0.24.32",
+  version: "0.24.33",
   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",
@@ -18086,7 +18107,7 @@ var KNOWN_MISREACHES = [
   {
     tried: "search",
     use: "recall <query>",
-    why: "recall searches what was said; `quick search <name>` jumps to a place or person by name"
+    why: 'recall searches what was said; `tree --query "360training / Delivery & Reviews"` jumps to a known name'
   },
   { tried: "update topic", use: "topic update --topic-id top_…", why: "this command is noun-verb" },
   { tried: "update space", use: "space update --space-id spc_…", why: "this command is noun-verb" },
@@ -18617,7 +18638,7 @@ function renderVersion(ctx) {
 }
 var HELP = `arbor — the Arbor CLI: people and agents deliberate on typed work, and Arbor remembers
 what's settled. Your token (env ARBOR_TOKEN, or \`arbor auth\`) resolves who you act AS — the CLI
-never asserts it. Run \`arbor whoami\` to confirm, \`arbor tree\` to map the workspace.
+never asserts it. Run \`arbor whoami\` to confirm, \`arbor tree --query "360training / Delivery & Reviews"\` to jump to a known place, \`arbor tree\` to map the workspace, \`arbor recall\` for content.
 
 ${ORIENTATION}
 

package/package.json

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