eve-hub 0.16.19 → 0.16.21

package/channels/eve-roster-user.js

@@ -7,6 +7,8 @@ import { isHubRequest } from "../hub-oidc.mjs";
 // a local-dev request, or one from the hub (a deployed bot, see hub-oidc.mjs). Resolving it as a user lets user-scoped
 // connections (open_pull_request's OAuth) key tokens to the configured human;
 // `localDev()` alone is not a user, so eve fails them with principal_required.
+// eve serves `GET /eve/v1/info` only to operator principals; the hub reads it as this user to learn the bot's
+// schedules and tools (hosted-hub readDeployment), so a request that passed the hub check may read it too.
 const dev = localDev();
 async function rosterUser(req) {
     const user = req.headers.get("x-roster-user");
@@ -14,7 +16,7 @@ async function rosterUser(req) {
         return null;
     if (!(await dev(req)) && !(await isHubRequest(req, getVercelOidcToken)))
         return null;
-    return { authenticator: "roster", principalId: `roster:${user}`, principalType: "user", attributes: {} };
+    return { authenticator: "roster", principalId: `roster:${user}`, principalType: "user", attributes: {}, allowAgentInfo: true };
 }
 // No turnPolicy: eve's default steers a message into the running turn at its
 // next step. The registry sends turnPolicy "queue" for a bot's message, so it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve-hub",
-  "version": "0.16.19",
+  "version": "0.16.21",
   "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/vercel.mjs

@@ -5,12 +5,17 @@
 // Vercel build: elsewhere this file's cwd is a person's checkout.
 import { withEve } from "eve/vercel";
 import { prepareDeployment } from "./prepare.mjs";
+import { coordinatorOf, readWorkspaceFile } from "./workspace.mjs";
 
-if (process.env.VERCEL) prepareDeployment(process.cwd());
+const dir = process.cwd();
+if (process.env.VERCEL) prepareDeployment(dir);
 
 // Each agents/<name>/agent is its own service at /eve/<name>/v1/*. eve
-// publishes only its own transport routes, so main's /hub/manifest channel
-// route (agents/main/agent/channels/manifest.ts) is routed here.
+// publishes only its own transport routes, so the coordinator's /hub/manifest
+// channel route (agents/<coordinator>/agent/channels/manifest.ts, which
+// prepare.mjs writes) is routed here.
+const coordinator = coordinatorOf(readWorkspaceFile(dir).agents);
+if (!coordinator) throw new Error(`${dir}: hub.workspace.json names no coordinator to serve /hub/manifest`);
 export default await withEve({
-  routes: [{ src: "^/hub/manifest$", destination: { type: "service", service: "eve-main" } }],
+  routes: [{ src: "^/hub/manifest$", destination: { type: "service", service: `eve-${coordinator}` } }],
 });