@hank-warren/pi-loop 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @hank-warren/pi-loop
 
+## 0.2.1
+
+### Patch Changes
+
+- 2b22273: Stop the loop with "goal completed" when pi-goal clears its state entry after completion. pi-goal persists the finished goal (status complete) and then writes a clear (goal: null), so by the loop's next tick the last goal-state entry was the clear and the loop paused as goal-missing instead of stopping as goal-complete. readGoalSnapshot now reads a completed goal through its completion clear; a clear over any non-complete goal (user /goal clear mid-flight) still pauses the loop.
+
 ## 0.2.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hank-warren/pi-loop",
-  "version": "0.2.0",
+  "version": "0.2.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/state.ts

@@ -87,11 +87,17 @@ interface SessionEntryLike {
 }
 
 function lastCustomEntryData(entries: unknown[], customType: string): unknown {
-	for (let index = entries.length - 1; index >= 0; index -= 1) {
+	return lastCustomEntryDatas(entries, customType, 1)[0];
+}
+
+/** Newest-first data of the last `limit` custom entries of `customType`. */
+function lastCustomEntryDatas(entries: unknown[], customType: string, limit: number): unknown[] {
+	const datas: unknown[] = [];
+	for (let index = entries.length - 1; index >= 0 && datas.length < limit; index -= 1) {
 		const entry = entries[index] as SessionEntryLike | undefined;
-		if (entry?.type === "custom" && entry.customType === customType) return entry.data;
+		if (entry?.type === "custom" && entry.customType === customType) datas.push(entry.data);
 	}
-	return undefined;
+	return datas;
 }
 
 /** Restore the persisted loop state from a session branch, fail-open. */
@@ -120,11 +126,26 @@ export interface GoalSnapshot {
  * entry shape is not recognizably a goal. Only fields pi-loop consumes are
  * extracted; unknown statuses are preserved verbatim so the caller can treat
  * anything outside its known sets conservatively.
+ *
+ * Completion race: pi-goal persists the finished goal (status "complete") and
+ * then clears the entry (goal: null), so by the loop's next tick the last
+ * entry is the clear. A clear whose immediately preceding entry is a complete
+ * goal therefore reports that complete goal — the loop must stop with
+ * "goal completed", not pause as goal-missing. A clear over any other status
+ * (user /goal clear mid-flight) still reads as no goal.
  */
 export function readGoalSnapshot(entries: unknown[]): GoalSnapshot | undefined {
-	const data = ownRecord(lastCustomEntryData(entries, GOAL_STATE_ENTRY_TYPE));
-	if (!data) return undefined;
-	const goal = ownRecord(data.goal);
+	const datas = lastCustomEntryDatas(entries, GOAL_STATE_ENTRY_TYPE, 2);
+	const newest = ownRecord(datas[0]);
+	if (!newest) return undefined;
+	const goal = parseGoalSnapshot(newest.goal);
+	if (goal) return goal;
+	const cleared = parseGoalSnapshot(ownRecord(datas[1])?.goal);
+	return cleared?.status === "complete" ? cleared : undefined;
+}
+
+function parseGoalSnapshot(value: unknown): GoalSnapshot | undefined {
+	const goal = ownRecord(value);
 	if (!goal) return undefined;
 	const status = typeof goal.status === "string" ? goal.status : undefined;
 	const text = typeof goal.text === "string" ? goal.text.trim() : "";