pi-posthorse 0.10.7 → 0.10.9

package/README.md

@@ -23,7 +23,7 @@ Give Pi your task. For example:
 
 ## How rollover works
 
-Posthorse can nudge the model to update task notes before rollover, then continue working. The nudge does not require `new_context` or wake an agent after its final answer. Large turns can reach rollover before the nudge.
+Posthorse can send a routine task-note reminder before rollover. The reminder tells the model to save current task state if needed, then immediately continue the prescribed work. The context window is not a task deadline. The reminder does not require `new_context` or wake an agent after its final answer. Large turns can reach rollover before the reminder. See [Reminder timing](docs/reminder-timing.md) for the trigger and its relationship to Pi's reserve and retention settings.
 
 Automatic rollover retains a safe recent-message tail using Pi's `compaction.keepRecentTokens`, alongside a bounded recovery record for discarded inputs and tool evidence. It never calls a summarization model. The model must restore notes and check live state before it continues. Optional `new_context` deliberately retains no prior messages; manual `/compact` uses Pi's normal summarization.
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-posthorse",
-	"version": "0.10.7",
+	"version": "0.10.9",
 	"type": "module",
 	"description": "Posthorse: fresh context, same journey. No-summary context rollover for Pi, with sparse budget reminders, handoffs, notes, and history.",
 	"keywords": [

package/src/budget.ts

@@ -13,8 +13,13 @@ import {
 import { imagesOf, textOf } from "./message-text.ts";
 
 const MIN_USABLE_TOKENS = Math.ceil(MAX_HANDOFF_CHARS / 4) * 2;
-export const CHECKPOINT_STEPS =
-	"update the task's current-state note (goal, progress, decisions, next steps) with available file-editing tools at its absolute path; use notes write only for creation, substantial restructuring, or when editing tools are unavailable. If the note is already current, leave it unchanged. Then continue working; let automatic rollover happen without calling new_context";
+export const CHECKPOINT_GUIDANCE = `Keep working on the assigned task; Pi handles context rollover automatically.
+
+The current context window is not a deadline for finishing your task. Do not reduce scope, skip prescribed steps or verification, or issue a final progress summary because rollover is approaching.
+
+Update the task's current-state note if needed: goal, progress, decisions, and next steps. Use available file-editing tools at its absolute path; use notes write only for creation, substantial restructuring, or when editing tools are unavailable. Leave an already-current note unchanged. Then immediately execute the next prescribed task step in this run. No new_context call, waiting for rollover, or user "continue" is needed.
+
+Finish when the requested work and required verification are complete, or report a genuine blocker. Approaching context rollover is not a blocker.`;
 export type Budget = {
 	readonly contextWindow: number;
 	readonly reserveTokens: number;
@@ -76,15 +81,11 @@ function automaticGuidance(budget: Budget | undefined, enabled: boolean): string
 	if (budget !== undefined && !budget.supported) {
 		return unsupportedMessage(budget);
 	}
-	const deadline =
-		budget === undefined
-			? "the configured Pi context limit"
-			: `${Math.max(1, Math.round((budget.rolloverAt / budget.contextWindow) * 100))}% used`;
 	const line =
 		budget === undefined
 			? ""
 			: ` The rollover line is ${budget.rolloverAt.toLocaleString("en-US")} tokens used under the available Pi settings.`;
-	return `Automatic rollover follows Pi's compaction setting and retains a safe recent-message tail using compaction.keepRecentTokens, without model summarization.${line} At most one notes reminder may arrive at the end of a working turn before the rollover line (${deadline}), never on a turn that ends the run; when it does, ${CHECKPOINT_STEPS}. new_context is an optional deliberate clean reset, not a checkpoint requirement.`;
+	return `${CHECKPOINT_GUIDANCE}\nAutomatic rollover follows Pi's compaction setting and retains a safe recent-message tail using compaction.keepRecentTokens, without model summarization.${line} At most one routine task-note reminder may arrive at the end of a working turn, never on a turn that ends the run. new_context is an optional deliberate clean reset, not a checkpoint requirement.`;
 }
 export function buildGuidance(ctx: PolicyContext): string {
 	const budget = budgetFor(ctx);
@@ -93,10 +94,10 @@ export function buildGuidance(ctx: PolicyContext): string {
 		budget === undefined
 			? "Configured context capacity is unknown."
 			: `Configured context capacity: ${budget.contextWindow.toLocaleString("en-US")} tokens. This is Pi's best available native limit, not remaining space or a measured provider boundary. Fresh windows use the active configuration; system instructions, tools, the handoff, retained recent messages, and new messages consume part of it.`;
-	return `## Context self-management (Posthorse)
+	return `## Automatic context management (Posthorse)
+${automaticGuidance(budget, enabled)}
 ${capacity}
 Do not guess context capacity or remaining space from response-token limits or reasoning budgets. Before reporting a remaining-token count or changing your work plan because of context limits, call get_context_remaining. If usage is unknown, report it as unknown. No routine budget checks are needed.
-${automaticGuidance(budget, enabled)}
 After a rollover, earlier conversation stays in history. Restore notes and todos, then verify live state before stateful or external work; automatic handoffs record inputs, not progress.
 Keep one concise current-state note per task. Preserve decisions and safety constraints; link fuller evidence and history instead of copying them. Edit changed sections rather than resending unchanged content.
 Write handoffs and notes as normal readable prose; notes and history search match literal text.`;

package/src/rollover.ts

@@ -5,7 +5,7 @@ import type {
 	ExtensionContext,
 	TurnEndEvent,
 } from "@earendil-works/pi-coding-agent";
-import { budgetFor, CHECKPOINT_STEPS, freshPayloadChars, type Budget } from "./budget.ts";
+import { budgetFor, CHECKPOINT_GUIDANCE, freshPayloadChars, type Budget } from "./budget.ts";
 import {
 	isRecord,
 	isReminderType,
@@ -83,9 +83,7 @@ function endsRun(
 		ctx.hasPendingMessages?.() !== true
 	);
 }
-function reminderBudget(
-	host: PolicyContext,
-): { readonly budget: Budget; readonly tokens: number } | undefined {
+function reminderBudget(host: PolicyContext): Budget | undefined {
 	const usage = host.getContextUsage();
 	if (usage === undefined || usage.tokens === null || usage.contextWindow <= 0) {
 		return undefined;
@@ -100,14 +98,13 @@ function reminderBudget(
 		return undefined;
 	}
 	const buffer = Math.min(REMINDER_BUFFER_TOKENS, Math.floor(budget.usable * 0.1));
-	return usage.tokens < budget.rolloverAt - buffer ? undefined : { budget, tokens: usage.tokens };
+	return usage.tokens < budget.rolloverAt - buffer ? undefined : budget;
 }
 function sendReminder(
 	pi: ExtensionAPI,
 	ctx: ExtensionContext,
 	available: {
 		readonly budget: Budget;
-		readonly tokens: number;
 		readonly pendingMessages: readonly {
 			readonly role: string;
 			readonly customType?: string | undefined;
@@ -116,7 +113,7 @@ function sendReminder(
 	},
 	reminders: ReminderLookup,
 ): void {
-	const { budget, tokens } = available;
+	const { budget } = available;
 	const state = reminders.read(ctx);
 	const fingerprint: ReminderFingerprint = {
 		windowId: state.windowId,
@@ -137,7 +134,7 @@ function sendReminder(
 	pi.sendMessage(
 		{
 			customType: REMINDER_TYPE,
-			content: `[posthorse] Notes checkpoint: ${(budget.rolloverAt - tokens).toLocaleString("en-US")} tokens remain before Pi's automatic rollover line. Please ${CHECKPOINT_STEPS}.`,
+			content: `[posthorse] Routine task-note update.\n${CHECKPOINT_GUIDANCE}`,
 			display: true,
 			details: fingerprint,
 		},
@@ -481,7 +478,7 @@ export function registerRollover(
 			sendReminder(
 				pi,
 				ctx,
-				{ ...available, pendingMessages: event.context.pendingMessages },
+				{ budget: available, pendingMessages: event.context.pendingMessages },
 				reminders,
 			);
 		}