@hank-warren/pi-loop 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @hank-warren/pi-loop
 
+## 0.4.1
+
+### Patch Changes
+
+- 3fbf632: Clear `nextWakeAt` when the wake timer fires, so `/loop status` can no longer report a "Next wake" clock time that has already passed. A tick that coalesces instead of firing — a busy or compacting session — left the old deadline in place, printing it directly above the line saying a wake is pending at the next idle boundary. Display only; no scheduling behaviour changes.
+
 ## 0.4.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hank-warren/pi-loop",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Interval wakeups for Pi: recurring prompt re-runs, stall rescue toward an active pi-goal goal, and loop-aware compaction that survives long sessions.",
   "type": "module",
   "keywords": [

package/src/loop.ts

@@ -144,6 +144,12 @@ export class LoopController {
 		this.nextWakeAt = this.now() + delayMs;
 		this.timer = setTimeout(() => {
 			this.timer = undefined;
+			// Nothing is scheduled once the timer has fired. `runTick` re-arms it
+			// through `scheduleTick` when it pokes, but a busy or compacting
+			// session coalesces into `wakePending` instead — and leaving the old
+			// deadline here made `/loop status` report a clock time that had
+			// already passed.
+			this.nextWakeAt = undefined;
 			const ctx = this.sessionCtx;
 			if (!ctx) return;
 			this.runTick(ctx);