eve-hub 0.8.1 → 0.9.0

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # eve-hub
 
+## 0.9.0
+
+### Minor Changes
+
+- The bots no longer write the hub's tables. A bot's append goes to its own session stream, and the hub folds that stream into turns and replies after a wake (`/api/fold`). Needs a hub that serves `/api/fold`.
+
+## 0.8.2
+
+### Patch Changes
+
+- The per-bot mention gate is gone: the hub decides who a bot's message wakes (wake router), so the `hooks/mention-gate` hook is removed from the kit.
+
 ## 0.8.1
 
 ### Patch Changes

package/kit-modules.json

@@ -2,7 +2,6 @@
   "channels/eve",
   "channels/eve-roster-user",
   "connections/vercel-kit",
-  "hooks/mention-gate",
   "hooks/sandbox",
   "instructions/engineering",
   "instructions/main",

package/mention-gate.d.mts

@@ -2,5 +2,4 @@ export type GateConfig = { enabled: boolean; model: string; api: 'chat' | 'decis
 export function gateConfig(env?: Record<string, string | undefined>, file?: unknown): GateConfig;
 export function opensWithHandle(text: string, agent: string): boolean;
 export function cleanReason(reason: unknown): string;
-export function screenInbound(input: { text: string; sessionId: string; agent?: string; registryUrl: string; credential: (opts?: { refresh?: boolean }) => Promise<{ token: string; teamId?: string | null } | null>; instructions?: string; fetchImpl?: typeof fetch; log?: ((line: string) => void) | null }): Promise<{ cancel: boolean; result?: unknown }>;
 export function hubCredentialLoader(fetchHub: (path: string, init: { headers?: Record<string, string> }) => Promise<Response>): (opts?: { refresh?: boolean }) => Promise<{ ok: boolean; token?: string; error?: string }>;

package/mention-gate.mjs

@@ -1,19 +1,7 @@
-// Mention gate: when a bot's turn is woken by an @-mention or a DM, the bot
-// itself (its message.received hook, hooks/mention-gate.ts) asks a cheap
-// model, through AI Gateway, whether a reply is needed, before its main model
-// runs. The model reads the bot's own instructions and the delivery the bot
-// just received. A handle inside code (codeRanges) is dropped by
-// parseMentions before it joins or wakes anyone; the gate catches the other
-// incidental ones: a quote or a recap, or an ack that asks nothing.
-//
-// The hub decides which wakes are gated (gatedWake, registry/server.mjs) and
-// owns the outcome: the hook asks it first (POST /api/mention-gate/check),
-// then reports the decision (POST /api/mention-gate/report); on a skip the
-// hub posts the system line and records the usage, and the hook cancels the
-// turn. Biased to answering: the model only classifies the message (how the
-// handle is used, what it asks of the bot); skipFor decides, and any error,
-// timeout or unreadable verdict answers. Only bots' messages are gated: the
-// human's always wake.
+// The decision-model helpers the registry's mention gate (registry/server.mjs, frozen until its removal) and the hosted hub's wake
+// router and closing check share: the gateway config (gateConfig), the Mac bot credential loader and the response parsing. The bot-side
+// hook is gone; the hosted hub decides who a message wakes (hosted-hub/src/store/wake-router.ts). A handle inside code (codeRanges)
+// is dropped by parseMentions before it joins or wakes anyone.
 //
 // Config (the hub's, sent to the hook with each check): `mentionGate` in
 // hub.workspace.json ({ enabled, model, reasoningEffort, timeoutMs }),
@@ -21,7 +9,6 @@
 // HUB_MENTION_GATE_REASONING, HUB_MENTION_GATE_TIMEOUT_MS and
 // HUB_MENTION_GATE_URL (tests).
 import { codeRanges } from "./mention-tokens.mjs";
-import { hubHeaders } from "./registry-fetch.mjs";
 import { createHash } from "node:crypto";
 
 export { codeRanges };
@@ -395,45 +382,6 @@ export function credentialCache(load, { ttlMs = 10 * 60e3, failMs = 60e3, now =
   return get;
 }
 
-// --- The bot's side (hooks/mention-gate.ts).
-
-const HUB_CALL_MS = 2000;
-
-async function hubCall(fetchImpl, url, body) {
-  const res = await fetchImpl(url, { method: "POST", headers: await hubHeaders({ "content-type": "application/json" }), body: JSON.stringify(body), signal: AbortSignal.timeout(HUB_CALL_MS) });
-  if (!res.ok) throw new Error(`hub ${res.status}`);
-  return res.json();
-}
-
-// One inbound delivery, screened. Never throws; { cancel: true } only when the
-// hub accepted a skip (it posted the system line and expects the turn to
-// end cancelled). Anything that fails on the way answers.
-//   text: the delivery (message.received's data.message)
-//   credential: ({ refresh }) → { token, teamId? } | null (credentialCache)
-// `agent` is optional: left out, the hub names the bot from its session and sends its instructions.
-export async function screenInbound({ text, sessionId, agent, registryUrl, instructions = "", credential, fetchImpl = fetch, log = console.warn }) {
-  const messageId = triggerId(text);
-  if (!registryUrl || !messageId) return { cancel: false };
-  let check;
-  try {
-    check = await hubCall(fetchImpl, `${registryUrl}/api/mention-gate/check`, { ...(agent ? { agent } : {}), messageId, sessionId });
-  } catch (error) {
-    log?.(`[mention-gate] check for ${messageId} failed, answering: ${error?.message ?? error}`);
-    return { cancel: false };
-  }
-  if (!check?.gate || !check.config) return { cancel: false };
-  agent ??= check.agent;
-  instructions ||= check.instructions ?? "";
-  const r = await decide({ config: check.config, credential, prompt: promptFor(check.config, { agent, human: check.humanName ?? "the human", instructions, envelope: text, broadcast: Boolean(check.broadcast) }), addressed: Boolean(check.addressed), fetchImpl });
-  try {
-    const ack = await hubCall(fetchImpl, `${registryUrl}/api/mention-gate/report`, { ...(agent ? { agent } : {}), messageId, sessionId, skip: r.skip, reason: r.reason, verdict: r.verdict ?? null, usage: r.usage ?? null, ms: r.ms, error: r.error ?? null });
-    return { cancel: Boolean(r.skip && ack?.skip), result: r };
-  } catch (error) {
-    log?.(`[mention-gate] report for ${messageId} failed, answering: ${error?.message ?? error}`);
-    return { cancel: false, result: r };
-  }
-}
-
 // A Mac bot's AI Gateway credential: the hub mints an OIDC token for the workspace's bots project, asked for with the bot's HUB_TOKEN.
 // `fetchHub(path, init)` is registryFetch. On a refresh it names the token AI Gateway refused, as eve's served credential does.
 export function hubCredentialLoader(fetchHub) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve-hub",
-  "version": "0.8.1",
+  "version": "0.9.0",
   "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/stubs.mjs

@@ -4,7 +4,6 @@
 export const KIT_FILES = {
   "channels/eve.ts": ["Queued eve channel that resolves the registry's human as a user.", "channels/eve-roster-user.ts"],
   "hooks/sandbox.ts": ["Migrates legacy Docker sessions to the host sandbox."],
-  "hooks/mention-gate.ts": ["Mention gate: a cheap model decides whether an inbound @-mention or DM needs a turn."],
   "tools/bash.ts": ["eve's bash with a default time limit (kills the process group) and the workspace's code location."],
   "tools/react.ts": ["React to a message with an emoji."],
   "tools/show.ts": ["Move the human's screen to a thread, DM, or message."],
@@ -52,7 +51,6 @@ export const MAIN_KIT_FILES = {
 // main's dash schedule stays: off the hub's machine it has no PR data (its lookup runs `gh`).
 export const DEPLOYED_KIT_FILES = new Set([
   "channels/eve.ts",
-  "hooks/mention-gate.ts",
   "schedules/dash.ts",
   "skills/onboarding-profile.ts",
   "tools/onboarding_scripts.ts",