eve-hub 0.12.0 → 0.13.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/README.md +1 -1
  3. package/package.json +2 -3
  4. package/prepare.mjs +2 -10
  5. package/vendor/world-turso.mjs +0 -6416
  6. package/world.mjs +0 -10721
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # eve-hub
2
2
 
3
+ ## 0.13.0
4
+
5
+ ### Minor Changes
6
+
7
+ - b2a7266: Bots run plain eve on Vercel's Workflow storage: the kit no longer wires in a workflow world or exports `eve-hub/world`.
8
+
3
9
  ## 0.12.0
4
10
 
5
11
  ### Minor Changes
package/README.md CHANGED
@@ -61,7 +61,7 @@ A deployed workspace (lib/workspace-template.mjs, staged by hosted-hub/scripts/s
61
61
 
62
62
  Releases go through Changesets, as in eve. A PR that changes the kit adds a changeset (`pnpm changeset`) and applies it (`pnpm changeset version`); when it merges, `.github/workflows/release.yml` runs `changeset publish` (no bot commits to main: its ruleset allows only PR merges): the kit's `prepack` stages the package into `dist/npm` (its `publishConfig.directory`), npm gets it, and the `eve-hub@<version>` GitHub release is created. npm auth is the repo's `NPM_TOKEN` secret (an npm automation token). The template pins the version this checkout carries.
63
63
 
64
- The template's main gets a Vercel Sandbox and only the kit stubs that run without the hub's machine (lib/workspace-template.mjs `DEPLOYED_KIT_FILES`; eve's own bash replaces the kit's). The template's builder also mounts eve-code (`eve/extensions/code`: `apply_patch`, `grep`, the review skills, a read-only worker) and `eve/extensions/git` (`git({})`), both with no `github` option. The bot uses `gh` and `git` from bash, whose GitHub token is the sandbox firewall's (the Vercel sandbox `create_agent` writes, lib/agent-template.mjs `sandboxFile`), and no `gh` tool is contributed. A deployed workspace's eve is the one pin in `hosted-hub/bots/package.json`, which staging copies over the template's (an eve snapshot with both `eve/world-hub` and `eve/extensions/git`; `hosted-hub/test/stage-workspace.test.mjs` checks the staged imports resolve against it). The hub and local bots stay on the hub's eve. The published tarball (`scripts/pack.mjs`) leaves out the kit__worker extension, which mounts only on the hub's machine. The hub reaches each bot's eve channel with `Authorization: Bearer $BOT_TOKEN` (`bot-token.mjs`); the kit's calls to the hub (`registry-fetch.mjs`, at `ROSTER_REGISTRY_URL`) carry `Authorization: Bearer $HUB_TOKEN` when set. The hosted hub keeps Vercel Authentication on: a deployed bot sends its project's OIDC token in `x-vercel-trusted-oidc-idp-token` too (the hub project lists each bots project in its Trusted Sources, `hosted-hub/src/onboard/trust.ts` `trustBots`, and never the bypass secret, even while its deployment still holds the env), and a bot on a Mac sends `x-vercel-protection-bypass: $HUB_PROTECTION_BYPASS` (the hub project's automation bypass secret) when it has one.
64
+ The template's main gets a Vercel Sandbox and only the kit stubs that run without the hub's machine (lib/workspace-template.mjs `DEPLOYED_KIT_FILES`; eve's own bash replaces the kit's). The template's builder also mounts eve-code (`eve/extensions/code`: `apply_patch`, `grep`, the review skills, a read-only worker) and `eve/extensions/git` (`git({})`), both with no `github` option. The bot uses `gh` and `git` from bash, whose GitHub token is the sandbox firewall's (the Vercel sandbox `create_agent` writes, lib/agent-template.mjs `sandboxFile`), and no `gh` tool is contributed. A deployed workspace's eve is the one pin in `hosted-hub/bots/package.json`, which staging copies over the template's (an eve snapshot with `eve/extensions/git`; `hosted-hub/test/stage-workspace.test.mjs` checks the staged imports resolve against it). The hub and local bots stay on the hub's eve. The published tarball (`scripts/pack.mjs`) leaves out the kit__worker extension, which mounts only on the hub's machine. The hub reaches each bot's eve channel with `Authorization: Bearer $BOT_TOKEN` (`bot-token.mjs`); the kit's calls to the hub (`registry-fetch.mjs`, at `ROSTER_REGISTRY_URL`) carry `Authorization: Bearer $HUB_TOKEN` when set. The hosted hub keeps Vercel Authentication on: a deployed bot sends its project's OIDC token in `x-vercel-trusted-oidc-idp-token` too (the hub project lists each bots project in its Trusted Sources, `hosted-hub/src/onboard/trust.ts` `trustBots`, and never the bypass secret, even while its deployment still holds the env), and a bot on a Mac sends `x-vercel-protection-bypass: $HUB_PROTECTION_BYPASS` (the hub project's automation bypass secret) when it has one.
65
65
 
66
66
  ## Vercel Kit connection
67
67
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eve-hub",
3
- "version": "0.12.0",
3
+ "version": "0.13.0",
4
4
  "license": "Apache-2.0",
5
5
  "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.",
6
6
  "type": "module",
@@ -29,8 +29,7 @@
29
29
  "./bot-token": "./bot-token.mjs",
30
30
  "./hub-oidc": "./hub-oidc.mjs",
31
31
  "./prepare": "./prepare.mjs",
32
- "./vercel": "./vercel.mjs",
33
- "./world": "./world.mjs"
32
+ "./vercel": "./vercel.mjs"
34
33
  },
35
34
  "peerDependencies": {
36
35
  "eve": "*",
package/prepare.mjs CHANGED
@@ -9,8 +9,8 @@
9
9
  // token opens it and pays for model calls) with only the kit stubs that run
10
10
  // off the hub's machine (DEPLOYED_KIT_FILES); a hosted bot whose sandbox.ts
11
11
  // is the host's fails the build, and the build never writes a sandbox;
12
- // - the kit extension, host-only workers and kit stubs are dropped, the hub's
13
- // workflow world is wired in (and the Vercel Kit connection), every bot gets eve's git extension, and the
12
+ // - the kit extension, host-only workers and kit stubs are dropped, the
13
+ // Vercel Kit connection is wired in, every bot gets eve's git extension, and the
14
14
  // workspace's memory and each bot's team architecture are embedded in the bots' memory providers (a function
15
15
  // has no workspace cwd);
16
16
  // - /hub/manifest: the roster and the commit sha the deployment was built
@@ -79,12 +79,6 @@ export default defineChannel({
79
79
 
80
80
  export const MANIFEST_FILE = "hub.manifest.json";
81
81
 
82
- export function injectWorkflowWorld(agent, file) {
83
- const count = agent.split("defineAgent({").length - 1;
84
- if (count !== 1) throw new Error(`${file}: expected exactly one defineAgent({, found ${count}`);
85
- return agent.replace("defineAgent({", `defineAgent({\n experimental: { workflow: { world: "eve-hub/world" } },`);
86
- }
87
-
88
82
  // Removes `file` under `bot`, then any directory it leaves empty.
89
83
  function removeStub(bot, file) {
90
84
  unlinkSync(join(bot, file));
@@ -159,8 +153,6 @@ export function prepareDeployment(dir) {
159
153
  for (const item of readdirSync(bot, { recursive: true })) {
160
154
  if (item.endsWith(join("extensions", "kit.ts"))) removeStub(bot, item);
161
155
  }
162
- const agentFile = join(bot, "agent.ts");
163
- writeFileSync(agentFile, injectWorkflowWorld(readFileSync(agentFile, "utf8"), agentFile));
164
156
  // Slack for the onboarding skill comes through Vercel Kit, with the project's KIT_CONNECTOR;
165
157
  // without one the connection resolves to nothing.
166
158
  mkdirSync(join(bot, "connections"), { recursive: true });