eve-hub 0.6.55 → 0.6.56

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # eve-hub
 
+## 0.6.56
+
+### Patch Changes
+
+- Deployed bots always carry the Vercel Kit connection (it resolves to nothing without a `KIT_CONNECTOR`), so a workspace's onboarding-profile skill reaches Slack; onboarding and the upgrade give the bots project the hub's Kit connector.
+
 ## 0.6.55
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve-hub",
-  "version": "0.6.55",
+  "version": "0.6.56",
   "license": "Apache-2.0",
   "description": "Bot-side code shared by every hub agent: registry tools, the roster hook, the eve channel, the host sandbox and browser, and model helpers.",
   "type": "module",

package/prepare.mjs

@@ -10,8 +10,7 @@
 //   off the hub's machine (DEPLOYED_KIT_FILES); a hosted bot whose sandbox.ts
 //   is the host's fails the build, and the build never writes a sandbox;
 // - the kit extension, host-only workers and kit stubs are dropped, the hub's
-//   workflow world is wired in (and the Vercel Kit connection, if GITHUB_PATH
-//   says "kit"), every bot gets eve's git extension, and the
+//   workflow world is wired in (and the Vercel Kit connection), every bot gets eve's git extension, and the
 //   workspace's memory is embedded in the bots' memory providers (a function
 //   has no workspace cwd);
 // - /hub/manifest: the roster and the commit sha the deployment was built
@@ -19,7 +18,6 @@
 //   vercel.mjs. Bearer BOT_TOKEN, as on each bot's eve channel (bot-token.mjs).
 import { existsSync, mkdirSync, readdirSync, readFileSync, rmSync, rmdirSync, unlinkSync, writeFileSync } from "node:fs";
 import { basename, dirname, join } from "node:path";
-import { GITHUB_PATH } from "./github-path.mjs";
 import { DEPLOYED_KIT_FILES, KIT_FILES, MAIN_KIT_FILES } from "./stubs.mjs";
 import KIT_MODULES from "./kit-modules.json" with { type: "json" };
 import { applyKit, readBotFiles, syncKit } from "./sync-kit.mjs";
@@ -152,12 +150,10 @@ export function prepareDeployment(dir) {
     }
     const agentFile = join(bot, "agent.ts");
     writeFileSync(agentFile, injectWorkflowWorld(readFileSync(agentFile, "utf8"), agentFile));
-    // GITHUB_PATH "kit": the human's connected services (GitHub) come through Vercel Kit,
-    // with the project's KIT_CONNECTOR. "gh" deploys no Kit connection.
-    if (GITHUB_PATH === "kit") {
-      mkdirSync(join(bot, "connections"), { recursive: true });
-      writeFileSync(join(bot, "connections", "vercel-kit.ts"), 'export { default } from "eve-hub/connections/vercel-kit";\n');
-    }
+    // Slack for the onboarding skill comes through Vercel Kit, with the project's KIT_CONNECTOR;
+    // without one the connection resolves to nothing.
+    mkdirSync(join(bot, "connections"), { recursive: true });
+    writeFileSync(join(bot, "connections", "vercel-kit.ts"), 'export { default } from "eve-hub/connections/vercel-kit";\n');
     mkdirSync(join(bot, "memory"), { recursive: true });
     const botDir = join(dir, "agents", name);
     writeFileSync(join(bot, "memory", "workspace.ts"), memoryProvider("workspace", readMemory(dir, { folders: domainFolders(botDomains(dir, botDir)) }).entries, "Standing decision", "workspace"));

package/github-path.d.mts

@@ -1 +0,0 @@
-export const GITHUB_PATH: "gh" | "kit";

package/github-path.mjs

@@ -1,8 +0,0 @@
-// How every deployed bot reaches GitHub, decided here and nowhere else:
-//   "gh"  `gh` and `git` in bash (the firewall token and eve's git extension, both
-//         always on, prepare.mjs); no Vercel Kit connection, so no bot can pick
-//         Kit for GitHub, and onboarding sets up no Kit connector.
-//   "kit" the same, plus the Kit connection on every bot (prepare.mjs, and the
-//         peer dependencies it needs in hosted-hub/scripts/stage-workspace.mjs) and
-//         the Kit connector on each new bots project (hosted-hub/src/onboard/provision-steps.ts).
-export const GITHUB_PATH = "gh";