eve-hub 0.5.2 → 0.5.4

package/CHANGELOG.md

@@ -0,0 +1,13 @@
+# eve-hub
+
+## 0.5.4
+
+### Patch Changes
+
+- 8f951a0: Change explainer: a `prs[]` entry without `number` publishes as a commit range (no fake PR number), and step names may index with brackets, e.g. `CODES[code]`.
+
+## 0.5.3
+
+### Patch Changes
+
+- 383e906: Published through Changesets from the release workflow; no API changes.

package/README.md

@@ -52,13 +52,13 @@ A bot's role is enforced by its files as well as its prose. `create_agent`'s `pr
 3. The stubs use the specifiers the `exports` map serves (`eve-hub/tools/x`, `eve-hub/host-sandbox`, `eve-hub/roster-model`, …).
 4. `eve` and `zod` are peer dependencies. eve's bundler resolves the kit to its realpath, so the kit's own `eve` imports come from hub's install. When the workspace's eve is linked to hub's, that's one eve (verified with eve 0.69).
 
-Bump `version` when a tool's name, schema, or description, the hook's events, or the channel config changes. Hub records each agent's kit version and accepts N and N−1 (D0/D12).
+Add a changeset (`pnpm changeset`, pick `eve-hub`) when a tool's name, schema, or description, the hook's events, or the channel config changes; the release bumps `version` from it. Hub records each agent's kit version and accepts N and N−1 (D0/D12).
 
 ## Published package (deployed workspaces)
 
 A deployed workspace (`node scripts/workspace-template.mjs <dir>`, lib/workspace-template.mjs) has no hub checkout to link, so it installs the kit from npm, published as [`eve-hub`](https://www.npmjs.com/package/eve-hub): `"eve-hub": "<version>"`. `node packages/agent-kit/scripts/pack.mjs <outDir>` builds the package: every `.ts` module compiled to `.js` + `.d.ts` in place (node won't strip types under `node_modules`), the `exports` map pointed at them, and `templates/` included.
 
-`.github/workflows/publish-eve-hub.yml` publishes it on every push to main whose kit `version` npm doesn't have yet, authenticated by the repo's `NPM_TOKEN` secret (an npm automation token). Bump `version` to ship a kit change to deployed workspaces; the template pins the version this checkout carries.
+Releases go through Changesets, as in eve. A PR that changes the kit adds a changeset (`pnpm changeset`); when it merges, `.github/workflows/release.yml` bumps `version`, writes CHANGELOG.md, commits both to main and runs `changeset publish`: 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.
 
 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 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` and, since the hosted hub keeps Vercel Authentication on, `x-vercel-protection-bypass: $HUB_PROTECTION_BYPASS` (the hub project's automation bypass secret), each when set.
 

package/artifacts/types/change-explainer.mjs

@@ -21,14 +21,15 @@ export function firstSentence(text = "") {
   return sentence.length > 220 ? `${sentence.slice(0, 219).replace(/\s+\S*$/, "")}…` : sentence;
 }
 
-// Card fields from the fixture: what the change is, and which commits.
-export function cardOf(fixture, overview) {
+// Card fields from the fixture: what the change is, and which commits. A
+// change with no PRs (a local repo) names its branch instead.
+export function cardOf(fixture, overview, branch) {
   const short = (sha) => String(sha ?? "").slice(0, 9);
-  const prs = (fixture.prs ?? []).map((p) => `#${p.number}`);
+  const prs = (fixture.prs ?? []).filter((p) => p.number !== undefined).map((p) => `#${p.number}`);
   return {
     title: fixture.title ?? fixture.id,
     gist: firstSentence(overview?.thesis),
-    subtitle: [fixture.repo, prs.join(" ")].filter(Boolean).join(" "),
+    subtitle: [fixture.repo, ...(prs.length ? prs : [branch])].filter(Boolean).join(" "),
     ref: `${short(fixture.base)}..${short(fixture.head)}`,
   };
 }
@@ -51,7 +52,7 @@ async function build(source, { sandbox }) {
     });
     const listing = await run(sandbox, ["find", data, "-type", "f", "-print0"]);
     for (const file of listing.split("\0").filter(Boolean)) files.push({ file: `data/${file.slice(data.length + 1)}`, data: await sandbox.readBinaryFile({ path: file }) });
-    return { files, card: cardOf(fixture, overview), meta: { repo: fixture.repo, base, head, prs: (fixture.prs ?? []).map((p) => p.number) } };
+    return { files, card: cardOf(fixture, overview, source.branch), meta: { repo: fixture.repo, base, head, prs: (fixture.prs ?? []).flatMap((p) => p.number ?? []) } };
   } finally {
     await sandbox.removePath({ path: work, recursive: true, force: true });
   }