@agentconnect.md/setup 2.2.0-rc.10 → 2.2.0-rc.11

package/dist/index.js

@@ -39194,28 +39194,9 @@ function number(params) {
 //#endregion
 //#region ../protocol/dist/slack-app-manifest.js
 var import_fastify = /* @__PURE__ */ __toESM(require_fastify(), 1);
-/** App-level Slack message shortcut for opening the controls of the session that
-* owns the selected message's conversation. Direct apps receive it over Socket
-* Mode; shared apps receive the same callback through the relay HTTP edge.
-*
-* Declared to Slack by {@link buildSlackAppManifest} below, which is why it lives
-* here rather than beside the runtime Block Kit action ids in `frames/relay-cp.ts`:
-* those name controls on messages we post, this one names a manifest feature. */
 const SLACK_MANAGE_SESSION_SHORTCUT_CALLBACK_ID = "ac_manage_session";
 /** Public platform profile copy. Never derive this from an Agent description. */
 const PLATFORM_APP_DESCRIPTION = "AI agent powered by AgentConnect.";
-/**
-* Every bot scope the app requests, and the exact set an installation must hold.
-*
-* There was briefly a required/capability split here, on the theory that a scope backing one
-* optional tool should not mark an older installation broken. It did not survive contact: the
-* "required" half was not required either — the app receives and answers messages without
-* several of them — so the line was invented rather than observed, and it bought a second
-* constant, an extra API field, extra console branches, and a message that said six permissions
-* were missing without naming them. One list is both simpler and more honest: these are the
-* scopes AgentConnect needs, an install short of any of them is incomplete, and the console
-* says exactly which to add.
-*/
 const SLACK_BOT_SCOPES = [
 	"files:read",
 	"app_mentions:read",
@@ -39246,8 +39227,6 @@ const SLACK_BOT_SCOPES = [
 	"lists:read",
 	"lists:write",
 	"channels:join",
-	"team:read",
-	"users:read.email",
 	"search:read.public",
 	"search:read.files",
 	"search:read.users"