@integrity-labs/agt-cli 0.28.865 → 0.28.867

package/dist/mcp/direct-chat-channel.js

@@ -32631,7 +32631,9 @@ var OAUTH_PROVIDERS = {
     publicClient: true,
     mcpUrl: "https://mcp.kajabi.com/mcp",
     // Curated surface (matches the catalog seed's defined_scopes[].tools). Kajabi's
-    // live MCP advertises ~111 tools; the agent only needs these 28.
+    // live MCP advertises ~111 tools; the agent only needs these 34.
+    // (Was written as 28 and left stale when the four pages/themes tools landed
+    // in ENG-7629's follow-up — recounted here rather than left to drift again.)
     // CS-1427: `enable_toolset` is included so an agent can activate its own
     // products/commerce + analytics toolsets on the connection (Kajabi gates those
     // tool groups behind a runtime toolset that returns "not active" until enabled).
@@ -32676,7 +32678,26 @@ var OAUTH_PROVIDERS = {
       "list_landing_pages",
       "get_landing_page",
       "update_landing_page",
-      "get_theme_content"
+      "get_theme_content",
+      // CS-1689: the write half of the two groups above. Every Kajabi write we
+      // curate stopped at the email-content boundary — an agent could
+      // create_sequence and get_theme_content but could not add an email to a
+      // sequence or apply a theme edit, so any change to an EXISTING email had
+      // to go back to the customer by hand.
+      //
+      // Both names are Kajabi's own, taken from the descriptions of tools we
+      // already advertise rather than guessed: `create_sequence` says "Add
+      // emails with add_sequence_email", and `create_broadcast` +
+      // `get_theme_content` both say to "pair with update_theme_content to
+      // apply changes". That sourcing matters here — a name the server does not
+      // advertise is logged and SKIPPED by the proxy, so a wrong guess would
+      // look applied and change nothing.
+      //
+      // No new catalog scope: these join the existing kajabi:emails and
+      // kajabi:pages scopes, so already-connected sites do not need to
+      // re-authorise to pick them up.
+      "add_sequence_email",
+      "update_theme_content"
     ],
     // CS-1446: Kajabi gates several tool groups behind a runtime `enable_toolset`
     // and does not advertise their tools in `tools/list` until the group is

package/dist/mcp/index.js

@@ -25205,7 +25205,9 @@ var OAUTH_PROVIDERS = {
     publicClient: true,
     mcpUrl: "https://mcp.kajabi.com/mcp",
     // Curated surface (matches the catalog seed's defined_scopes[].tools). Kajabi's
-    // live MCP advertises ~111 tools; the agent only needs these 28.
+    // live MCP advertises ~111 tools; the agent only needs these 34.
+    // (Was written as 28 and left stale when the four pages/themes tools landed
+    // in ENG-7629's follow-up — recounted here rather than left to drift again.)
     // CS-1427: `enable_toolset` is included so an agent can activate its own
     // products/commerce + analytics toolsets on the connection (Kajabi gates those
     // tool groups behind a runtime toolset that returns "not active" until enabled).
@@ -25250,7 +25252,26 @@ var OAUTH_PROVIDERS = {
       "list_landing_pages",
       "get_landing_page",
       "update_landing_page",
-      "get_theme_content"
+      "get_theme_content",
+      // CS-1689: the write half of the two groups above. Every Kajabi write we
+      // curate stopped at the email-content boundary — an agent could
+      // create_sequence and get_theme_content but could not add an email to a
+      // sequence or apply a theme edit, so any change to an EXISTING email had
+      // to go back to the customer by hand.
+      //
+      // Both names are Kajabi's own, taken from the descriptions of tools we
+      // already advertise rather than guessed: `create_sequence` says "Add
+      // emails with add_sequence_email", and `create_broadcast` +
+      // `get_theme_content` both say to "pair with update_theme_content to
+      // apply changes". That sourcing matters here — a name the server does not
+      // advertise is logged and SKIPPED by the proxy, so a wrong guess would
+      // look applied and change nothing.
+      //
+      // No new catalog scope: these join the existing kajabi:emails and
+      // kajabi:pages scopes, so already-connected sites do not need to
+      // re-authorise to pick them up.
+      "add_sequence_email",
+      "update_theme_content"
     ],
     // CS-1446: Kajabi gates several tool groups behind a runtime `enable_toolset`
     // and does not advertise their tools in `tools/list` until the group is

package/dist/mcp/origami.js

@@ -39336,7 +39336,9 @@ var OAUTH_PROVIDERS = {
     publicClient: true,
     mcpUrl: "https://mcp.kajabi.com/mcp",
     // Curated surface (matches the catalog seed's defined_scopes[].tools). Kajabi's
-    // live MCP advertises ~111 tools; the agent only needs these 28.
+    // live MCP advertises ~111 tools; the agent only needs these 34.
+    // (Was written as 28 and left stale when the four pages/themes tools landed
+    // in ENG-7629's follow-up — recounted here rather than left to drift again.)
     // CS-1427: `enable_toolset` is included so an agent can activate its own
     // products/commerce + analytics toolsets on the connection (Kajabi gates those
     // tool groups behind a runtime toolset that returns "not active" until enabled).
@@ -39381,7 +39383,26 @@ var OAUTH_PROVIDERS = {
       "list_landing_pages",
       "get_landing_page",
       "update_landing_page",
-      "get_theme_content"
+      "get_theme_content",
+      // CS-1689: the write half of the two groups above. Every Kajabi write we
+      // curate stopped at the email-content boundary — an agent could
+      // create_sequence and get_theme_content but could not add an email to a
+      // sequence or apply a theme edit, so any change to an EXISTING email had
+      // to go back to the customer by hand.
+      //
+      // Both names are Kajabi's own, taken from the descriptions of tools we
+      // already advertise rather than guessed: `create_sequence` says "Add
+      // emails with add_sequence_email", and `create_broadcast` +
+      // `get_theme_content` both say to "pair with update_theme_content to
+      // apply changes". That sourcing matters here — a name the server does not
+      // advertise is logged and SKIPPED by the proxy, so a wrong guess would
+      // look applied and change nothing.
+      //
+      // No new catalog scope: these join the existing kajabi:emails and
+      // kajabi:pages scopes, so already-connected sites do not need to
+      // re-authorise to pick them up.
+      "add_sequence_email",
+      "update_theme_content"
     ],
     // CS-1446: Kajabi gates several tool groups behind a runtime `enable_toolset`
     // and does not advertise their tools in `tools/list` until the group is

package/dist/mcp/slack-channel.js

@@ -33478,7 +33478,9 @@ var OAUTH_PROVIDERS = {
     publicClient: true,
     mcpUrl: "https://mcp.kajabi.com/mcp",
     // Curated surface (matches the catalog seed's defined_scopes[].tools). Kajabi's
-    // live MCP advertises ~111 tools; the agent only needs these 28.
+    // live MCP advertises ~111 tools; the agent only needs these 34.
+    // (Was written as 28 and left stale when the four pages/themes tools landed
+    // in ENG-7629's follow-up — recounted here rather than left to drift again.)
     // CS-1427: `enable_toolset` is included so an agent can activate its own
     // products/commerce + analytics toolsets on the connection (Kajabi gates those
     // tool groups behind a runtime toolset that returns "not active" until enabled).
@@ -33523,7 +33525,26 @@ var OAUTH_PROVIDERS = {
       "list_landing_pages",
       "get_landing_page",
       "update_landing_page",
-      "get_theme_content"
+      "get_theme_content",
+      // CS-1689: the write half of the two groups above. Every Kajabi write we
+      // curate stopped at the email-content boundary — an agent could
+      // create_sequence and get_theme_content but could not add an email to a
+      // sequence or apply a theme edit, so any change to an EXISTING email had
+      // to go back to the customer by hand.
+      //
+      // Both names are Kajabi's own, taken from the descriptions of tools we
+      // already advertise rather than guessed: `create_sequence` says "Add
+      // emails with add_sequence_email", and `create_broadcast` +
+      // `get_theme_content` both say to "pair with update_theme_content to
+      // apply changes". That sourcing matters here — a name the server does not
+      // advertise is logged and SKIPPED by the proxy, so a wrong guess would
+      // look applied and change nothing.
+      //
+      // No new catalog scope: these join the existing kajabi:emails and
+      // kajabi:pages scopes, so already-connected sites do not need to
+      // re-authorise to pick them up.
+      "add_sequence_email",
+      "update_theme_content"
     ],
     // CS-1446: Kajabi gates several tool groups behind a runtime `enable_toolset`
     // and does not advertise their tools in `tools/list` until the group is

package/dist/mcp/telegram-channel.js

@@ -33616,7 +33616,9 @@ var OAUTH_PROVIDERS = {
     publicClient: true,
     mcpUrl: "https://mcp.kajabi.com/mcp",
     // Curated surface (matches the catalog seed's defined_scopes[].tools). Kajabi's
-    // live MCP advertises ~111 tools; the agent only needs these 28.
+    // live MCP advertises ~111 tools; the agent only needs these 34.
+    // (Was written as 28 and left stale when the four pages/themes tools landed
+    // in ENG-7629's follow-up — recounted here rather than left to drift again.)
     // CS-1427: `enable_toolset` is included so an agent can activate its own
     // products/commerce + analytics toolsets on the connection (Kajabi gates those
     // tool groups behind a runtime toolset that returns "not active" until enabled).
@@ -33661,7 +33663,26 @@ var OAUTH_PROVIDERS = {
       "list_landing_pages",
       "get_landing_page",
       "update_landing_page",
-      "get_theme_content"
+      "get_theme_content",
+      // CS-1689: the write half of the two groups above. Every Kajabi write we
+      // curate stopped at the email-content boundary — an agent could
+      // create_sequence and get_theme_content but could not add an email to a
+      // sequence or apply a theme edit, so any change to an EXISTING email had
+      // to go back to the customer by hand.
+      //
+      // Both names are Kajabi's own, taken from the descriptions of tools we
+      // already advertise rather than guessed: `create_sequence` says "Add
+      // emails with add_sequence_email", and `create_broadcast` +
+      // `get_theme_content` both say to "pair with update_theme_content to
+      // apply changes". That sourcing matters here — a name the server does not
+      // advertise is logged and SKIPPED by the proxy, so a wrong guess would
+      // look applied and change nothing.
+      //
+      // No new catalog scope: these join the existing kajabi:emails and
+      // kajabi:pages scopes, so already-connected sites do not need to
+      // re-authorise to pick them up.
+      "add_sequence_email",
+      "update_theme_content"
     ],
     // CS-1446: Kajabi gates several tool groups behind a runtime `enable_toolset`
     // and does not advertise their tools in `tools/list` until the group is

package/dist/{persistent-session-GSXFKCVO.js → persistent-session-J4GCUX72.js}

@@ -54,8 +54,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-PXDYKP5O.js";
-import "./chunk-JG3EAFZO.js";
+} from "./chunk-XHVKILCG.js";
+import "./chunk-VCPESUZV.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -114,4 +114,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-GSXFKCVO.js.map
+//# sourceMappingURL=persistent-session-J4GCUX72.js.map

package/dist/{responsiveness-probe-GOM3ZYW3.js → responsiveness-probe-UEB5LRGG.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-PXDYKP5O.js";
-import "./chunk-JG3EAFZO.js";
+} from "./chunk-XHVKILCG.js";
+import "./chunk-VCPESUZV.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -764,4 +764,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-GOM3ZYW3.js.map
+//# sourceMappingURL=responsiveness-probe-UEB5LRGG.js.map

package/dist/{session-auth-dead-ID4L35CN.js → session-auth-dead-S24CY4WK.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-JG3EAFZO.js";
+} from "./chunk-VCPESUZV.js";
 
 // src/lib/session-auth-dead.ts
 import { closeSync, openSync, readSync, readdirSync, statSync } from "fs";
@@ -203,4 +203,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-ID4L35CN.js.map
+//# sourceMappingURL=session-auth-dead-S24CY4WK.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.865",
+  "version": "0.28.867",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {
@@ -24,7 +24,7 @@
   "scripts": {
     "build": "tsup && npm run build:mcp-assets && npm run build:cli-assets",
     "build:mcp-assets": "mkdir -p dist/mcp && cp ../../packages/mcp/dist/index.js dist/mcp/index.js && cp ../../packages/mcp/dist/slack-channel.js dist/mcp/slack-channel.js && cp ../../packages/mcp/dist/direct-chat-channel.js dist/mcp/direct-chat-channel.js && cp ../../packages/mcp/dist/telegram-channel.js dist/mcp/telegram-channel.js && cp ../../packages/mcp/dist/teams-channel.js dist/mcp/teams-channel.js && cp ../../packages/mcp/dist/whatsapp-channel.js dist/mcp/whatsapp-channel.js && cp ../../packages/mcp/dist/whatsapp-link.js dist/mcp/whatsapp-link.js && cp ../../packages/mcp/dist/remote-oauth-proxy.js dist/mcp/remote-oauth-proxy.js && cp ../../packages/mcp/dist/computer-use-proxy.js dist/mcp/computer-use-proxy.js && cp ../../packages/augmented-admin-mcp/dist/index.js dist/mcp/augmented-admin.js && cp ../../packages/augmented-support-mcp/dist/index.js dist/mcp/augmented-support.js && cp ../../packages/augmented-help-kb-mcp/dist/index.js dist/mcp/augmented-help-kb.js && cp ../../packages/origami-mcp-server/dist/index.js dist/mcp/origami.js && cp ../../packages/xero-mcp-server/dist/index.js dist/mcp/xero.js",
-    "build:cli-assets": "mkdir -p dist/assets && cp assets/impersonate-statusline.sh dist/assets/impersonate-statusline.sh && chmod +x dist/assets/impersonate-statusline.sh && mkdir -p dist/assets/review && cp assets/review/post-review-findings.mjs dist/assets/review/post-review-findings.mjs && cp assets/review/obiwan-auth.mjs dist/assets/review/obiwan-auth.mjs && cp assets/review/SKILL.md dist/assets/review/SKILL.md && chmod +x dist/assets/review/post-review-findings.mjs",
+    "build:cli-assets": "mkdir -p dist/assets && cp assets/impersonate-statusline.sh dist/assets/impersonate-statusline.sh && chmod +x dist/assets/impersonate-statusline.sh && mkdir -p dist/assets/review && cp assets/review/post-review-findings.mjs dist/assets/review/post-review-findings.mjs && cp assets/review/obiwan-auth.mjs dist/assets/review/obiwan-auth.mjs && cp assets/review/SKILL.md dist/assets/review/SKILL.md && cp assets/review/SWEEP.md dist/assets/review/SWEEP.md && chmod +x dist/assets/review/post-review-findings.mjs",
     "dev": "tsx watch src/bin/agt.ts",
     "test": "vitest run",
     "typecheck": "bash ../../scripts/typecheck-guard.sh tsc --noEmit",