@ian-pascoe/pi-todo 0.6.0 → 0.6.1

package/README.md

@@ -43,7 +43,7 @@ A Pi `codemode` script receives the result as an object (the tool declares an `o
 
 Task status is `pending`, `active`, or `completed`; `add` defaults to `pending`. Tasks are flat, duplicate titles are allowed, and multiple Tasks may be active. Set `description` to `null` during `update` to remove it.
 
-Each tool group that changes the Todo List is projected from the immutable session state entries as one hidden full **Todo List Snapshot** of the group's final state, at a fixed conversation position after all of the group's sibling results. A tool group is one assistant turn's tool calls, including several `todo` calls inside one `codemode` script, so ten calls in a script add one Todo List Snapshot, not ten. A group that ends in the state it began with adds none. A change made outside a tool group, such as `/todo clear`, still projects its own Todo List Snapshot right away. Each Todo List Snapshot starts with the header `Todo List state from the pi-todo extension (not a user message):` so it does not read like user input. Later requests keep earlier Todo List Snapshots in place. Clearing the list produces an explicit empty Todo List Snapshot. The system prompt and tool description do not change.
+Each tool group that changes the Todo List is projected from the immutable session state entries as one hidden full **Todo List Snapshot** of the group's final state, at a fixed conversation position after all of the group's sibling results. A tool group is one assistant turn's tool calls, including several `todo` calls inside one `codemode` script, so ten calls in a script add one Todo List Snapshot, not ten. A group that ends in the state it began with adds none, and so does a group whose last `todo` result is a successful `list`, batch `add`, or batch `update` whose `details.tasks` equal the complete final Todo List, since the model already saw that list. Partial results, such as a single `update` or a batch `update` of some Tasks, still add one. A `codemode` group never skips, because its result is not a `todo` result. A change made outside a tool group, such as `/todo clear`, still projects its own Todo List Snapshot right away. Each Todo List Snapshot starts with the header `Todo List state from the pi-todo extension (not a user message):` so it does not read like user input. Later requests keep earlier Todo List Snapshots in place. Clearing the list produces an explicit empty Todo List Snapshot. The system prompt and tool description do not change.
 
 After compaction, a fixed baseline immediately after the summary restores the state from before the retained Tail. Retained and newer tool groups follow chronologically. This preserves previously written conversation cache prefixes between checkpoints; it does not guarantee provider cache hits.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ian-pascoe/pi-todo",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "private": false,
   "description": "Minimal session-native Todo List for Pi agents.",
   "keywords": [
@@ -33,7 +33,7 @@
     "provenance": true
   },
   "dependencies": {
-    "@ian-pascoe/pi-utils": "^0.5.0"
+    "@ian-pascoe/pi-utils": "^0.6.0"
   },
   "peerDependencies": {
     "@earendil-works/pi-ai": ">=1.1.0",

package/src/pi-todo-extension.ts

@@ -1,6 +1,12 @@
 import { StringEnum } from "@earendil-works/pi-ai";
-import type { ExtensionAPI, ExtensionContext, Theme } from "@earendil-works/pi-coding-agent";
+import {
+  defineTool,
+  type ExtensionAPI,
+  type ExtensionContext,
+  type Theme,
+} from "@earendil-works/pi-coding-agent";
 import { type Component } from "@earendil-works/pi-tui";
+import { acceptNullForOptionalArguments } from "@ian-pascoe/pi-utils/null-optional-arguments";
 import { noticeText } from "@ian-pascoe/pi-utils/ui";
 import { Type } from "typebox";
 import { projectTodoContext, todoStateFromEntry } from "./todo-context.js";
@@ -175,7 +181,7 @@ export default function piTodoExtension(pi: ExtensionAPI): void {
     }
   });
 
-  pi.registerTool<typeof TodoParameters, TodoToolDetails | undefined>({
+  const todoTool = defineTool<typeof TodoParameters, TodoToolDetails | undefined>({
     name: "todo",
     label: "Todo",
     description: "Manage the current session branch's Todo List.",
@@ -211,6 +217,7 @@ export default function piTodoExtension(pi: ExtensionAPI): void {
     renderResult: (result, options, theme, context) =>
       renderTodoResult(result, options, theme, context),
   });
+  pi.registerTool(acceptNullForOptionalArguments(todoTool));
 
   pi.registerCommand("todo", {
     description: "Manage the Todo List",

package/src/todo-context.ts

@@ -16,6 +16,7 @@ import {
 type Message = ContextEvent["messages"][number];
 /** Marks a snapshot as extension state so the model does not read it as user-authored. */
 const SNAPSHOT_HEADER = "Todo List state from the pi-todo extension (not a user message):";
+const ListDetails = Type.Object({ tasks: Type.Array(Type.Unknown()) });
 const ProjectionDetails = Type.Object(
   {
     version: Type.Literal(1),
@@ -43,6 +44,15 @@ export function todoStateFromEntry(entry: SessionEntry): TodoStateSnapshot | und
   return parseTodoStateSnapshot(entry.data);
 }
 
+/** True when a successful `todo` result's details carry exactly the complete resulting list. */
+function resultRendersList(message: Message | undefined, tasks: TodoStateSnapshot["tasks"]) {
+  if (message?.role !== "toolResult" || message.toolName !== "todo" || message.isError)
+    return false;
+  return (
+    Value.Check(ListDetails, message.details) && isDeepStrictEqual(message.details.tasks, tasks)
+  );
+}
+
 function snapshotMessage(
   entry: SessionEntry,
   state: TodoStateSnapshot,
@@ -113,10 +123,17 @@ export function projectTodoContext(
   }
   const outstanding = new Map<string, number>();
   // A tool group projects only its final state, once its last result has landed.
+  let lastTodoResult: Message | undefined;
   let pending: { entry: SessionEntry; state: TodoStateSnapshot } | undefined;
-  const project = (entry: SessionEntry, state: TodoStateSnapshot): void => {
+  const project = (entry: SessionEntry, state: TodoStateSnapshot, finalResult?: Message): void => {
     const content = formatTodoList(state.tasks);
-    if (content !== previousContent && (previousContent !== undefined || state.tasks.length > 0))
+    // The model already saw this exact list in the group's last result; a Snapshot would repeat it.
+    const rendered = resultRendersList(finalResult, state.tasks);
+    if (
+      !rendered &&
+      content !== previousContent &&
+      (previousContent !== undefined || state.tasks.length > 0)
+    )
       insert(snapshotMessage(entry, state, null));
     previousContent = content;
   };
@@ -134,17 +151,19 @@ export function projectTodoContext(
       if (outstanding.size > 0 && pending)
         throw new Error("Todo mutation has an incomplete tool group");
       outstanding.clear();
+      lastTodoResult = undefined;
       for (const block of message.content)
         if (block.type === "toolCall")
           outstanding.set(block.id, (outstanding.get(block.id) ?? 0) + 1);
     } else if (message.role === "toolResult") {
+      if (message.toolName === "todo") lastTodoResult = message;
       const remaining = (outstanding.get(message.toolCallId) ?? 0) - 1;
       if (remaining > 0) outstanding.set(message.toolCallId, remaining);
       else outstanding.delete(message.toolCallId);
     }
     anchor = message;
     if (outstanding.size === 0 && pending) {
-      project(pending.entry, pending.state);
+      project(pending.entry, pending.state, lastTodoResult);
       pending = undefined;
     }
   }