eve-hub 0.15.0 → 0.15.2

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # eve-hub
 
+## 0.15.2
+
+### Patch Changes
+
+- A wake-up posts at every firing. The hub no longer skips one because the bot had a turn in the thread since setting it, so a turn that only reacted can't cancel a promised check. Only deleting it, or `until` passing, stops it. The tool description and the shared instructions say so.
+
+## 0.15.1
+
+### Patch Changes
+
+- `list_agents`: a post that @-mentions an unavailable Mac bot now waits until its setup works, instead of being refused.
+
 ## 0.15.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve-hub",
-  "version": "0.15.0",
+  "version": "0.15.2",
   "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/schedules/wake.d.ts

@@ -31,13 +31,13 @@ export declare function wakeAuth(principal: Principal): {
     issuer?: string | undefined;
     subject?: string | undefined;
 } | null;
-/** The one call a firing makes: the hub decides whether to post, keyed on the occurrence so a retry posts once.
+/** The one call a firing makes: the hub posts it, keyed on the occurrence so a retry posts once.
  * A definitive refusal (a 4xx: the session is unknown, the thread archived) is returned, not thrown: retrying it can't change it. */
 export declare function fireWake(payload: ArmedWake, occurrence: Occurrence, { fetchImpl, base }?: {
     fetchImpl?: typeof fetch;
     base?: string;
 }): Promise<{
-    status: "posted" | "skipped";
+    status: "posted";
 } | {
     status: "refused";
     error: string;

package/schedules/wake.js

@@ -10,9 +10,8 @@
 // before approval and again before writing, and refuses the write if the two differ.
 // When it was armed is the hub's: it records the schedule record the tool call returns.
 // When it fires, run() tells the hub (POST /api/wakes, hosted-hub/src/api/wakes.ts)
-// as the bot's deployment; the hub skips it if the bot has had a turn in the thread
-// since arming or its last firing, and otherwise posts a system @-mention that queues
-// behind any running turn. An occurrence scheduled past `until` deletes the schedule
+// as the bot's deployment; the hub posts a system @-mention for every occurrence, which
+// queues behind any running turn. An occurrence scheduled past `until` deletes the schedule
 // instead. run() never starts a session itself: a session eve starts here is one the
 // hub cannot see.
 import { byPrincipal, defineDynamicSchedules, schedules } from "eve/experimental/schedules";
@@ -28,7 +27,7 @@ export function wakeAuth(principal) {
         return null;
     return { principalType: principal.type, authenticator: principal.authenticator, principalId: principal.principalId, attributes: {}, ...(principal.issuer === undefined ? {} : { issuer: principal.issuer }), ...(principal.subject === undefined ? {} : { subject: principal.subject }) };
 }
-/** The one call a firing makes: the hub decides whether to post, keyed on the occurrence so a retry posts once.
+/** The one call a firing makes: the hub posts it, keyed on the occurrence so a retry posts once.
  * A definitive refusal (a 4xx: the session is unknown, the thread archived) is returned, not thrown: retrying it can't change it. */
 export async function fireWake(payload, occurrence, { fetchImpl = fetch, base } = {}) {
     const res = await registryFetch("/api/wakes", {
@@ -52,7 +51,7 @@ export async function expireOrFire(payload, occurrence, { remove, fire }) {
     return fire(payload, occurrence);
 }
 const definition = defineDynamicSchedules({
-    description: "A wake-up for this thread: arm it when you end a turn with your own work unfinished and nothing sure to wake you. One-shot: a delay set to the expected wait. Recurring: a cron expression. Always set `until`, the last time it may fire. The hub posts it into this thread unless you have had a turn here since it was set or last fired.",
+    description: "A wake-up for this thread: arm it when you end a turn with your own work unfinished and nothing sure to wake you. One-shot: a delay set to the expected wait. Recurring: a cron expression. Always set `until`, the last time it may fire. Every firing posts into this thread until you delete it or `until` passes.",
     inputSchema: WakeInput,
     scope: byPrincipal,
     tool: true,

package/templates/execution.md

@@ -21,8 +21,8 @@
 - **Waiting**
   - Never sleep or poll more than 60 seconds in one command. Check CI or a deploy once, report, and say what you're waiting on.
   - While work runs, post at least every 30 minutes: a result, or the one thing blocking you.
-  - Ending a turn with your own work unfinished and nothing sure to wake you (CI, a deploy, a background task, stopping partway): arm a wake-up with `schedule__wake__create`, the delay set to the expected wait, the note saying what to pick up and `until` a little after it. It posts into this thread unless you've had a turn here since.
-  - To check back repeatedly (a long CI run, a slow rollout), arm it with a cron expression, `until` the last time it may fire. It posts each time the thread has been quiet since the last one.
+  - Ending a turn with your own work unfinished and nothing sure to wake you (CI, a deploy, a background task, stopping partway): arm a wake-up with `schedule__wake__create`, the delay set to the expected wait, the note saying what to pick up and `until` a little after it. It posts into this thread at that time, whatever happens meanwhile; delete it if the wait is over.
+  - To check back repeatedly (a long CI run, a slow rollout), arm it with a cron expression, `until` the last time it may fire. It posts at every firing; delete it once you're done waiting.
   - Don't arm one while waiting on the human or on a bot you just mentioned: their reply wakes you.
 - **Ending a turn**
   - End only with results, a blocker you can't clear, or a question for the human; never "I'll do it next".

package/tools/list_agents.js

@@ -2,7 +2,7 @@ import { defineTool } from "eve/tools";
 import { z } from "zod";
 import { registryFetch } from "../registry-fetch.mjs";
 export default defineTool({
-    description: "List the workspace's bots right now: each one's role, kind (its place in the team: coordinator, planner, builder, reviewer, git-ops, demo, or other), where it runs (hosted or local), the tools its runtime reports (null when not yet reported), its model, the model and reasoning each of its declared subagents and its built-in `agent` copies resolve to under the workspace subagent cap (clamped from hub.workspace.json, never rejected), whether it's idle, busy (and where; a bot's threads run in parallel, so busy elsewhere doesn't mean it can't start work in a new thread) or unavailable (with `reason`: a Mac bot whose Mac couldn't set up the workspace; a post that @-mentions it is refused, so route the work elsewhere or ask the human), its server's memory (process.rssMb) and uptime (process.uptimeS; only on a local hub, since a hosted hub runs no bot process to measure), and any restart in progress (restart_agent, or the registry recycling a bot that grew too big or ran too long). The team changes; check it before routing work.",
+    description: "List the workspace's bots right now: each one's role, kind (its place in the team: coordinator, planner, builder, reviewer, git-ops, demo, or other), where it runs (hosted or local), the tools its runtime reports (null when not yet reported), its model, the model and reasoning each of its declared subagents and its built-in `agent` copies resolve to under the workspace subagent cap (clamped from hub.workspace.json, never rejected), whether it's idle, busy (and where; a bot's threads run in parallel, so busy elsewhere doesn't mean it can't start work in a new thread) or unavailable (with `reason`: a Mac bot whose Mac couldn't set up the workspace; a post that @-mentions it waits until setup works, so route urgent work elsewhere), its server's memory (process.rssMb) and uptime (process.uptimeS; only on a local hub, since a hosted hub runs no bot process to measure), and any restart in progress (restart_agent, or the registry recycling a bot that grew too big or ran too long). The team changes; check it before routing work.",
     inputSchema: z.object({}),
     async execute() {
         // Anything but a 2xx list of bots is an error naming the status and the