@dumbmice/pi-todo-loop 0.1.0 → 0.1.1

package/AGENTS.md

@@ -147,6 +147,7 @@ introduces an edge.
 | `deleted` tasks leave list, open set and signature | `deleted tasks are excluded from tasks, open and signature` |
 | malformed entries degrade to the empty snapshot | `malformed or missing state degrades to the empty snapshot` |
 | config defaults survive garbage; fields are coerced | `missing or malformed config falls back to defaults`, `valid fields override, invalid ones are ignored` |
+| the reconciliation clause appears only after one continuation | `the reconciliation clause is off on the first nudge`, `the reconciliation clause appears after one continuation, update before remove`, `the block asks for reconciliation only from the second request of a chain` |
 | model-authored task text is sanitised before it enters a request | `a hostile task subject cannot break out of the tag` |
 | the injection shows open tasks only, bounded, `activeForm` for in_progress | `injection lists open tasks with their status`, `injection is bounded and reports the overflow`, `injection uses activeForm only for in_progress`, `injection tolerates an empty subject` |
 | a status change moves the signature | `signature changes when a status changes` |

package/CHANGELOG.md

@@ -4,6 +4,22 @@ All notable changes to this project are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.1] - 2026-11-04
+
+### Added
+
+- The injected block escalates once: from the first continuation of a chain it asks the model to
+  reconcile a drifted list — update statuses, add what is missing, remove what no longer applies, in
+  that order — so a stale list has an exit short of burning the round cap. The first request of a
+  chain still only asks for status moves.
+
+### Fixed
+
+- The publish workflow survives a stale registry read: it asks for the version three times before
+  concluding it is absent, and treats a `previously published` refusal as success. It also reads
+  `npm pack --json` in both shapes (npm 10 returns an array, npm 11 an object keyed by package name),
+  which is what failed the first two publish runs before they could upload.
+
 ## [0.1.0] - 2026-11-04
 
 Initial release.
@@ -48,6 +64,9 @@ Initial release.
 - The continuation marker's constant body states the instruction ("Continue with the open todo
   tasks…") instead of a self-closing tag, so `injectState: false` no longer continues with no
   instruction at all, and a marker left in history is self-explanatory.
+- The injected block escalates once: from the first continuation onwards it asks the model to
+  reconcile a drifted list (update statuses, add what is missing, remove what no longer applies —
+  in that order), which gives a stale list a deterministic exit short of burning the round cap.
 - A list that goes open → closed in a turn whose only tool results were `todo` is announced once: the
   loop's success state and its failure state are the same observable.
 - A stale-list burn now says so: the round-cap reason appends `, list unchanged for N settles`.

package/docs/behaviour.md

@@ -52,6 +52,12 @@ compaction cannot remove it.
 - **The ids are the todo tool's own**, except where the stored list supplies an unusable or duplicate
   id: that row moves to a free number so each row can be addressed, which means a `todo` call using the
   shown number can fail when the tool wrote the list that way.
+- **The block escalates once.** On the first request of a chain it only asks for status
+  moves; from the first continuation onwards it adds a reconciliation clause — *"if this
+  list has drifted from the work, reconcile it now: update statuses, add what is missing,
+  and remove what no longer applies"* — with removal last. A first sighting should not
+  invite reshaping the list; after a nudge that left the list untouched, a drifted list is
+  the likelier explanation. Verified: 115 tests, including both sides of the gate.
 - **A list cleared by `todo` calls alone is announced.** If every task goes from open to closed in a
   turn whose only tool results were `todo`, a warning says so once. The loop's success state and its
   failure state are the same observable.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dumbmice/pi-todo-loop",
-	"version": "0.1.0",
+	"version": "0.1.1",
 	"description": "Keep pi working while a todo list still has open tasks, and keep that list in context across compaction.",
 	"type": "module",
 	"license": "MIT",

package/src/index.ts

@@ -125,7 +125,7 @@ export default function todoLoop(pi: any, options: TodoLoopOptions = {}): void {
 		// alternation-requiring providers reject. So markers stay in history; only a
 		// marker sitting at the tail (the continuation request about to be made) is
 		// replaced by the state block, so the request never ends on user → user.
-		const text = { type: "text", text: renderInjection(snapshot, config) };
+		const text = { type: "text", text: renderInjection(snapshot, config, { reconcile: state.rounds >= 1 }) };
 		const record = (message: unknown): Record<string, unknown> | null =>
 			typeof message === "object" && message !== null ? (message as Record<string, unknown>) : null;
 		const isMarker = (message: unknown): boolean => record(message)?.customType === MARKER_TYPE;

package/src/inject.ts

@@ -52,7 +52,26 @@ export function sanitizeLabel(text: string): string {
 	return points.replace(/[\uD800-\uDBFF](?![\uDC00-\uDFFF])|(?<![\uD800-\uDBFF])[\uDC00-\uDFFF]/g, "").trim();
 }
 
-export function renderInjection(snapshot: Snapshot, config: LoopConfig): string {
+export interface InjectionOptions {
+	/**
+	 * Add the reconciliation clause. Off for the first nudge of a chain, on afterwards:
+	 * handing a model an explicit "fix the list" instruction on its first sighting
+	 * invites it to reshape the list instead of doing the work, while after one nudge a
+	 * drifted list is the likelier explanation.
+	 */
+	reconcile?: boolean;
+}
+
+const RECONCILE_CLAUSE = [
+	"If this list has drifted from the work, reconcile it now: update statuses,",
+	"add what is missing, and remove what no longer applies.",
+].join("\n");
+
+export function renderInjection(
+	snapshot: Snapshot,
+	config: LoopConfig,
+	options: InjectionOptions = {},
+): string {
 	const shown = snapshot.open.slice(0, config.maxInjectedTasks);
 	const rows = shown.map(
 		(task) =>
@@ -72,6 +91,7 @@ export function renderInjection(snapshot: Snapshot, config: LoopConfig): string
 		"with the open tasks, and move a task to in_progress when you start it and to",
 		"completed only once it is actually verified — if a task cannot be verified now,",
 		"leave it open and say what is blocking it.",
+		...(options.reconcile ? [RECONCILE_CLAUSE] : []),
 		`</${INJECT_TAG}>`,
 	].join("\n");
 }