@lambdacurry/arbor 0.6.0 → 0.6.2

package/dist/arbor.js

@@ -16315,7 +16315,7 @@ var ACTIONS = [
   {
     name: "notifications",
     title: "List your notifications",
-    description: "List the awareness feed of activity involving you — stamps on your work, replies in your threads, @-mentions, and your completed requests — newest first, with an unseen count. This is FYI (no response owed); use `inbox` for what's actually asked of you.",
+    description: "List the awareness feed of activity involving you — stamps on your work, replies in your threads, @-mentions, and your completed requests — newest first, with an unseen count. Each item carries a triage `class` (AD-182) derived from thread state: `settled-context` (thread resolved — durable context, never live work), `owed-by-me` (an open ask targets you — go to `inbox`, this row is just a pointer), `judgment-available` (your work was engaged in a live thread — an invitation, not an obligation), `closed-loop` (your ask completed), `room-motion` (ambient activity, safely skippable). This is FYI (no response owed); `inbox` remains the only obligation surface.",
     inputSchema: { ...PAGINATION_INPUT },
     surfaces: ["mcp", "cli"],
     run: forward("notification.list")
@@ -16386,7 +16386,7 @@ var ACTIONS = [
   {
     name: "tree",
     title: "Navigate the workspace tree",
-    description: "Map the workspace — a GLANCEABLE structure map, not a full dump. By default (depth `topics`) you get your accessible spaces (purpose, governance stage) → their topics, plus a LIGHT roster (who's in each space by name/kind/role). Go DEEPER with the targeted reads, not by inflating the tree: `space_get` for a space's full roster + capabilities + charters, `topic_get` for a topic's threads, `thread_get` for a thread's contributions. Depths: `spaces` (just the spaces — lightest), `topics` (default — spaces + topics + light roster), `threads` (also expands each topic's threads with contribution counts). Scope with space or topic to map just that subtree.",
+    description: "Map the workspace — a GLANCEABLE structure map, not a full dump. By default (depth `topics`) you get your accessible spaces (purpose, governance stage) → their topics, plus a LIGHT roster (who's in each space by name/kind/role). Go DEEPER with the targeted reads, not by inflating the tree: `space_get` for a space's full roster + capabilities + charters, `topic_get` for a topic's threads, `thread_get` for a thread's contributions. Depths: `spaces` (just the spaces — lightest), `topics` (default — spaces + topics + light roster), `threads` (also expands each topic's threads with contribution counts, thread status, and open-request counts — `openRequestsForYou` answers \"does this space need me?\" without opening it, AD-182). Scope with space or topic to map just that subtree.",
     inputSchema: {
       space: exports_external.string().optional().describe("scope to one space id (spc_…)"),
       topic: exports_external.string().optional().describe("scope to one topic id (top_…)"),

package/package.json

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