@lambdacurry/arbor 0.16.3 → 0.16.4

package/dist/arbor.js

@@ -17733,16 +17733,16 @@ var ACTION_DEFINITIONS = [
   {
     name: "github_repositories",
     title: "List installed GitHub repositories",
-    description: "READ ONLY: List repositories projected from this organization's verified Arbor Computer GitHub App installation. This returns repository ids and metadata, never credentials; use the id with github_connect_repository.",
+    description: "READ ONLY: List the repositories this organization's verified Arbor Computer GitHub App installation makes connectable — any collaborator in the org may read it. This returns repository ids and metadata, never credentials, and it lists only repositories the installation currently covers; use the id with github_connect_repository. Listing is not authority: connecting still requires your own permission over the target scope.",
     inputSchema: { ...PAGINATION_INPUT },
     surfaces: ["mcp", "cli"],
-    toolset: "admin",
+    toolset: "projects",
     run: forward("github.repositories")
   },
   {
     name: "github_connect_repository",
     title: "Connect a GitHub repository",
-    description: "Connect or disconnect one installed GitHub repository at an Arbor organization, Space, Topic, or Thread. This explicit, recoverable connection is required before Arbor may use private repository context there; it does not grant an agent a Git credential. THE SCOPE IS THE DECISION: a Computer recipe only NAMES repositories, and a Thread materializes one only when a connection at its own scope or an ANCESTOR authorizes it — so connect at the Topic that owns the project and every Thread opened under it inherits the environment, while connecting at a single Thread authorizes that Thread alone and no sibling. Read get_computer's repositoryAuthorization to see which scope currently grants each configured repository. Owner/admin only.",
+    description: "Connect or disconnect one installed GitHub repository at an Arbor organization, Space, Topic, or Thread. This explicit, recoverable connection is required before Arbor may use private repository context there; it does not grant an agent a Git credential. THE SCOPE IS THE DECISION: a Computer recipe only NAMES repositories, and a Thread materializes one only when a connection at its own scope or an ANCESTOR authorizes it — so connect at the Topic that owns the project and every Thread opened under it inherits the environment, while connecting at a single Thread authorizes that Thread alone and no sibling. Read get_computer's repositoryAuthorization to see which scope currently grants each configured repository. YOU MAY CONNECT AT ANY SCOPE YOU ALREADY MANAGE: a Thread or Topic takes the same permission that configures its Computer, so if you can set the Topic's recipe you can authorize its repositories; a Space takes Space admin, and the organization stays owner/admin. Disconnecting takes the same permission as connecting. Nobody can authorize a repository further than they can manage, and GitHub's own installation coverage remains a separate hard gate.",
     inputSchema: {
       repositoryId: exports_external.string().describe("installed repository id from github_repositories, ghr_…"),
       scope: exports_external.enum(["organization", "space", "topic", "thread"]).describe("the Arbor scope that may use this repository's context; topic is the durable choice for a project every Thread under it develops"),
@@ -17750,7 +17750,7 @@ var ACTION_DEFINITIONS = [
       connected: exports_external.boolean().describe("true to connect; false to disconnect recoverably")
     },
     surfaces: ["mcp", "cli"],
-    toolset: "admin",
+    toolset: "projects",
     run: forward("github.set_repository_connection")
   },
   {

package/package.json

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