@lambdacurry/arbor 0.4.13 → 0.4.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/arbor.js +3 -3
- package/package.json +1 -1
package/dist/arbor.js
CHANGED
|
@@ -16376,7 +16376,7 @@ var ACTIONS = [
|
|
|
16376
16376
|
{
|
|
16377
16377
|
name: "cancel_request",
|
|
16378
16378
|
title: "Cancel a request",
|
|
16379
|
-
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).",
|
|
16379
|
+
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). Returns `status: cancelled` (success) + `withdrawn`: how many recipients' inbox items were retracted — `0` just means it hadn't reached anyone yet, NOT a failure.",
|
|
16380
16380
|
inputSchema: {
|
|
16381
16381
|
requestId: exports_external.string().describe("the open request to cancel, req_…")
|
|
16382
16382
|
},
|
|
@@ -16467,7 +16467,7 @@ var ACTIONS = [
|
|
|
16467
16467
|
{
|
|
16468
16468
|
name: "tree",
|
|
16469
16469
|
title: "Navigate the workspace tree",
|
|
16470
|
-
description: "Map the workspace in one call — your accessible spaces, their
|
|
16470
|
+
description: "Map the workspace in one call — your accessible spaces (with their purpose, governance stage, and ROSTER: who's in each space, their role, and what they can do) plus each space's topics and threads (with contribution counts) — to orient WITHOUT chaining space/topic/thread reads. The roster tells you who to route work to; for the full picture of how someone operates (their charter + how they work in a specific space) read `space_get`. Scope with space or topic; depth=topics stops above threads.",
|
|
16471
16471
|
inputSchema: {
|
|
16472
16472
|
space: exports_external.string().optional().describe("scope to one space id (spc_…)"),
|
|
16473
16473
|
topic: exports_external.string().optional().describe("scope to one topic id (top_…)"),
|
|
@@ -16681,7 +16681,7 @@ var ACTIONS = [
|
|
|
16681
16681
|
{
|
|
16682
16682
|
name: "space_get",
|
|
16683
16683
|
title: "Read a space",
|
|
16684
|
-
description: "Read one space by id — its details
|
|
16684
|
+
description: "Read one space by id — its details, the topics under it, and the full MEMBER roster: who's here, their role, their capabilities, and each member's space charter (how they operate in THIS space, AD-152) plus their identity charter. Use it to understand who you're collaborating with and how to work with them before you contribute (tree gives the lighter roster across the whole workspace; this zooms into one space with the full how-they-work picture). Space-access gated, like every read.",
|
|
16685
16685
|
inputSchema: {
|
|
16686
16686
|
id: exports_external.string().min(1).describe("the space id")
|
|
16687
16687
|
},
|
package/package.json
CHANGED