@alphacoder-v0/pi-loops 0.22.7 → 0.22.8

package/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to pi-loops are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.22.8] - 2026-10-28
+
+### Fixed
+- **A slot is not run twice when the clock changes hands.** A headless host that read `jobs.json`
+  just before an interactive pi took the clock could still dispatch from that snapshot. The pi
+  had already run the slot and cleared `running`, so the host claimed and ran it a second time,
+  and in one variant wrote an older `lastDueAt` back so a newer slot was owed again. A claim now
+  fails when the job's `lastDueAt` or `lastFiredAt` moved since the snapshot. Found with a TLA+
+  model of the scheduler. [#51](https://github.com/alphacoder-v0/pi-loops/issues/51),
+  [#87](https://github.com/alphacoder-v0/pi-loops/pull/87)
+- **A host that learns from its own tick that it lost the clock leaves cleanly.** It awaited
+  `exit()` inside the tick, and `exit()` stops the scheduler, which waits for that same tick. The
+  host then left only through the 10 s `process.exit` fallback: its runs in flight wrote no
+  record and no `run_end` event, and `host.json` was left behind, so the next pi reported a
+  crashed host. [#52](https://github.com/alphacoder-v0/pi-loops/issues/52),
+  [#87](https://github.com/alphacoder-v0/pi-loops/pull/87)
+
 ## [0.22.7] - 2026-10-28
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alphacoder-v0/pi-loops",
-  "version": "0.22.7",
+  "version": "0.22.8",
   "description": "An automation layer for pi: cron + stateful loops with a triage inbox, maker/checker verification, dynamic triggers, MCP notifications and tools, lifecycle hooks, session archives. A non-invasive pi extension.",
   "type": "module",
   "license": "MIT",

package/src/host-runtime.ts

@@ -139,7 +139,8 @@ export function createHostRuntime(deps: HostRuntimeDeps): HostRuntime {
 					if (exiting) return;
 					exiting = true;
 					log("an interactive pi owns the clock; exiting");
-					await deps.exit(0);
+					// Not awaited: exit() stops the scheduler, and scheduler.stop() waits for this tick.
+					Promise.resolve(deps.exit(0)).catch((err: any) => log(`exit failed: ${err?.message ?? err}`));
 					return;
 				}
 				await triggers.tick(now, leader);

package/src/scheduler.ts

@@ -776,6 +776,9 @@ export class LoopScheduler {
 		const priorFiredAt = job.lastFiredAt;
 		const claimed = await this.store.update(job.id, (j) => {
 			if (j.running) return;
+			// The slot was decided from a snapshot. If another process ran or skipped this job since,
+			// its stamps moved: that slot is spent, and running it again would run it twice.
+			if (j.lastDueAt !== priorDueAt || j.lastFiredAt !== priorFiredAt) return;
 			j.running = { runId, pid: process.pid, host: this.self.host, startedAt };
 			if (dueIso) j.lastDueAt = dueIso;
 			j.lastFiredAt = startedAt;