@oh-my-pi/pi-coding-agent 12.19.2 → 13.0.0

package/src/patch/hashline.ts

@@ -16,7 +16,7 @@ import type { HashMismatch } from "./types";
 
 export type LineTag = { line: number; hash: string };
 export type HashlineEdit =
-	| { op: "set"; tag: LineTag; content: string[] }
+	| { op: "replace"; tag: LineTag; content: string[] }
 	| { op: "replace"; first: LineTag; last: LineTag; content: string[] }
 	| { op: "append"; after?: LineTag; content: string[] }
 	| { op: "prepend"; before?: LineTag; content: string[] }
@@ -414,7 +414,7 @@ export function validateLineRef(ref: { line: number; hash: string }, fileLines:
 /**
  * Apply an array of hashline edits to file content.
  *
- * Each edit operation identifies target lines directly (`set`, `set_range`,
+ * Each edit operation identifies target lines directly (`replace`,
  * `insert`). Line references are resolved via {@link parseTag}
  * and hashes validated before any mutation.
  *
@@ -456,8 +456,17 @@ export function applyHashlineEdits(
 	}
 	for (const edit of edits) {
 		switch (edit.op) {
-			case "set": {
-				if (!validateRef(edit.tag)) continue;
+			case "replace": {
+				if ("tag" in edit) {
+					if (!validateRef(edit.tag)) continue;
+				} else {
+					if (edit.first.line > edit.last.line) {
+						throw new Error(`Range start line ${edit.first.line} must be <= end line ${edit.last.line}`);
+					}
+					const startValid = validateRef(edit.first);
+					const endValid = validateRef(edit.last);
+					if (!startValid || !endValid) continue;
+				}
 				break;
 			}
 			case "append": {
@@ -486,16 +495,6 @@ export function applyHashlineEdits(
 				if (!afterValid || !beforeValid) continue;
 				break;
 			}
-			case "replace": {
-				if (edit.first.line > edit.last.line) {
-					throw new Error(`Range start line ${edit.first.line} must be <= end line ${edit.last.line}`);
-				}
-
-				const startValid = validateRef(edit.first);
-				const endValid = validateRef(edit.last);
-				if (!startValid || !endValid) continue;
-				break;
-			}
 		}
 	}
 	if (mismatches.length > 0) {
@@ -508,11 +507,12 @@ export function applyHashlineEdits(
 		const edit = edits[i];
 		let lineKey: string;
 		switch (edit.op) {
-			case "set":
-				lineKey = `s:${edit.tag.line}`;
-				break;
 			case "replace":
-				lineKey = `r:${edit.first.line}:${edit.last.line}`;
+				if ("tag" in edit) {
+					lineKey = `s:${edit.tag.line}`;
+				} else {
+					lineKey = `r:${edit.first.line}:${edit.last.line}`;
+				}
 				break;
 			case "append":
 				if (edit.after) {
@@ -550,12 +550,12 @@ export function applyHashlineEdits(
 		let sortLine: number;
 		let precedence: number;
 		switch (edit.op) {
-			case "set":
-				sortLine = edit.tag.line;
-				precedence = 0;
-				break;
 			case "replace":
-				sortLine = edit.last.line;
+				if ("tag" in edit) {
+					sortLine = edit.tag.line;
+				} else {
+					sortLine = edit.last.line;
+				}
 				precedence = 0;
 				break;
 			case "append":
@@ -579,26 +579,26 @@ export function applyHashlineEdits(
 	// Apply edits bottom-up
 	for (const { edit, idx } of annotated) {
 		switch (edit.op) {
-			case "set": {
-				const origLines = originalFileLines.slice(edit.tag.line - 1, edit.tag.line);
-				const newLines = edit.content;
-				if (origLines.every((line, i) => line === newLines[i])) {
-					noopEdits.push({
-						editIndex: idx,
-						loc: `${edit.tag.line}#${edit.tag.hash}`,
-						currentContent: origLines.join("\n"),
-					});
-					break;
-				}
-				fileLines.splice(edit.tag.line - 1, 1, ...newLines);
-				trackFirstChanged(edit.tag.line);
-				break;
-			}
 			case "replace": {
-				const count = edit.last.line - edit.first.line + 1;
-				const newLines = edit.content;
-				fileLines.splice(edit.first.line - 1, count, ...newLines);
-				trackFirstChanged(edit.first.line);
+				if ("tag" in edit) {
+					const origLines = originalFileLines.slice(edit.tag.line - 1, edit.tag.line);
+					const newLines = edit.content;
+					if (origLines.every((line, i) => line === newLines[i])) {
+						noopEdits.push({
+							editIndex: idx,
+							loc: `${edit.tag.line}#${edit.tag.hash}`,
+							currentContent: origLines.join("\n"),
+						});
+						break;
+					}
+					fileLines.splice(edit.tag.line - 1, 1, ...newLines);
+					trackFirstChanged(edit.tag.line);
+				} else {
+					const count = edit.last.line - edit.first.line + 1;
+					const newLines = edit.content;
+					fileLines.splice(edit.first.line - 1, count, ...newLines);
+					trackFirstChanged(edit.first.line);
+				}
 				break;
 			}
 			case "append": {

package/src/patch/index.ts

@@ -194,9 +194,9 @@ export function hashlineParseContent(edit: string | string[] | null): string[] {
 	if (lines[lines.length - 1].trim() === "") return lines.slice(0, -1);
 	return lines;
 }
-const hashlineTargetEditSchema = Type.Object(
+const hashlineReplaceTagEditSchema = Type.Object(
 	{
-		op: Type.Literal("set"),
+		op: Type.Literal("replace"),
 		tag: hashlineTagFormat("line being replaced"),
 		content: hashlineReplaceContentFormat("Replacement"),
 	},
@@ -221,7 +221,7 @@ const hashlinePrependEditSchema = Type.Object(
 	{ additionalProperties: false },
 );
 
-const hashlineRangeEditSchema = Type.Object(
+const hashlineReplaceRangeEditSchema = Type.Object(
 	{
 		op: Type.Literal("replace"),
 		first: hashlineTagFormat("first line"),
@@ -242,8 +242,8 @@ const hashlineInsertEditSchema = Type.Object(
 );
 
 const hashlineEditSpecSchema = Type.Union([
-	hashlineTargetEditSchema,
-	hashlineRangeEditSchema,
+	hashlineReplaceTagEditSchema,
+	hashlineReplaceRangeEditSchema,
 	hashlineAppendEditSchema,
 	hashlinePrependEditSchema,
 	hashlineInsertEditSchema,
@@ -556,19 +556,21 @@ export class EditTool implements AgentTool<TInput> {
 			const anchorEdits: HashlineEdit[] = [];
 			for (const edit of edits) {
 				switch (edit.op) {
-					case "set": {
-						const { tag, content } = edit;
-						anchorEdits.push({ op: "set", tag: parseTag(tag), content: hashlineParseContent(content) });
-						break;
-					}
 					case "replace": {
-						const { first, last, content } = edit;
-						anchorEdits.push({
-							op: "replace",
-							first: parseTag(first),
-							last: parseTag(last),
-							content: hashlineParseContent(content),
-						});
+						if ("tag" in edit) {
+							anchorEdits.push({
+								op: "replace",
+								tag: parseTag(edit.tag),
+								content: hashlineParseContent(edit.content),
+							});
+						} else {
+							anchorEdits.push({
+								op: "replace",
+								first: parseTag(edit.first),
+								last: parseTag(edit.last),
+								content: hashlineParseContent(edit.content),
+							});
+						}
 						break;
 					}
 					case "append": {
@@ -656,11 +658,12 @@ export class EditTool implements AgentTool<TInput> {
 					for (const edit of anchorEdits) {
 						refs.length = 0;
 						switch (edit.op) {
-							case "set":
-								refs.push(edit.tag);
-								break;
 							case "replace":
-								refs.push(edit.first, edit.last);
+								if ("tag" in edit) {
+									refs.push(edit.tag);
+								} else {
+									refs.push(edit.first, edit.last);
+								}
 								break;
 							case "append":
 								if (edit.after) refs.push(edit.after);

package/src/patch/shared.ts

@@ -87,10 +87,11 @@ interface EditRenderArgs {
 }
 
 type HashlineEditPreview =
-	| { target: string; new_content: string[] }
-	| { first: string; last: string; new_content: string[] }
-	| { before?: string; after?: string; inserted_lines: string[] }
-	| { old_text: string; new_text: string; all?: boolean };
+	| { op: "replace"; tag: string; content: string[] }
+	| { op: "replace"; first: string; last: string; content: string[] }
+	| { op: "append"; after?: string; content: string[] }
+	| { op: "prepend"; before?: string; content: string[] }
+	| { op: "insert"; before: string; after: string; content: string[] };
 
 /** Extended context for edit tool rendering */
 export interface EditRenderContext {
@@ -158,56 +159,33 @@ function formatStreamingHashlineEdits(edits: unknown[], uiTheme: Theme): string
 
 	return text.trimEnd();
 	function formatHashlineEdit(edit: unknown): { srcLabel: string; dst: string } {
-		const asRecord = (value: unknown): Record<string, unknown> | undefined => {
-			if (typeof value === "object" && value !== null) return value as Record<string, unknown>;
-			return undefined;
-		};
-		const editRecord = asRecord(edit);
+		const editRecord = typeof edit === "object" && edit !== null ? (edit as Record<string, unknown>) : undefined;
 		if (!editRecord) {
-			return {
-				srcLabel: "• (incomplete edit)",
-				dst: "",
-			};
+			return { srcLabel: "• (incomplete edit)", dst: "" };
 		}
-		if ("target" in editRecord) {
-			const target = typeof editRecord.target === "string" ? editRecord.target : "…";
-			const newContent = editRecord.new_content;
-			return {
-				srcLabel: `• line ${target}`,
-				dst: Array.isArray(newContent) ? (newContent as string[]).join("\n") : "",
-			};
+
+		const contentLines = Array.isArray(editRecord.content) ? (editRecord.content as string[]).join("\n") : "";
+
+		// replace with tag (single line)
+		if ("tag" in editRecord && !("first" in editRecord)) {
+			const tag = typeof editRecord.tag === "string" ? editRecord.tag : "…";
+			return { srcLabel: `• line ${tag}`, dst: contentLines };
 		}
+		// replace with first..last (range)
 		if ("first" in editRecord || "last" in editRecord) {
 			const first = typeof editRecord.first === "string" ? editRecord.first : "…";
 			const last = typeof editRecord.last === "string" ? editRecord.last : "…";
-			const newContent = editRecord.new_content;
-			return {
-				srcLabel: `• range ${first}..${last}`,
-				dst: Array.isArray(newContent) ? (newContent as string[]).join("\n") : "",
-			};
-		}
-		if ("old_text" in editRecord || "new_text" in editRecord) {
-			const all = typeof editRecord.all === "boolean" ? editRecord.all : false;
-			return {
-				srcLabel: `• replace old_text→new_text${all ? " (all)" : ""}`,
-				dst: typeof editRecord.new_text === "string" ? editRecord.new_text : "",
-			};
+			return { srcLabel: `• range ${first}..${last}`, dst: contentLines };
 		}
-		if ("inserted_lines" in editRecord || "before" in editRecord || "after" in editRecord) {
+		// append/prepend/insert
+		if ("before" in editRecord || "after" in editRecord) {
 			const after = typeof editRecord.after === "string" ? editRecord.after : undefined;
 			const before = typeof editRecord.before === "string" ? editRecord.before : undefined;
-			const insertedLines = editRecord.inserted_lines;
-			const text = Array.isArray(insertedLines) ? (insertedLines as string[]).join("\n") : "";
 			const refs = [after, before].filter(Boolean).join("..") || "…";
-			return {
-				srcLabel: `• insert ${refs}`,
-				dst: text,
-			};
+			return { srcLabel: `• insert ${refs}`, dst: contentLines };
 		}
-		return {
-			srcLabel: "• (incomplete edit)",
-			dst: "",
-		};
+
+		return { srcLabel: "• (incomplete edit)", dst: "" };
 	}
 }
 function formatMetadataLine(lineCount: number | null, language: string | undefined, uiTheme: Theme): string {

package/src/plan-mode/approved-plan.ts

@@ -0,0 +1,55 @@
+import * as fs from "node:fs/promises";
+import { isEnoent } from "@oh-my-pi/pi-utils";
+import { resolveLocalUrlToPath } from "../internal-urls";
+
+interface RenameApprovedPlanFileOptions {
+	planFilePath: string;
+	finalPlanFilePath: string;
+	getArtifactsDir: () => string | null;
+	getSessionId: () => string | null;
+}
+
+function assertLocalUrl(path: string, label: "source" | "destination"): void {
+	if (!path.startsWith("local://")) {
+		throw new Error(`Approved plan ${label} path must use local:// (received ${path}).`);
+	}
+}
+
+export async function renameApprovedPlanFile(options: RenameApprovedPlanFileOptions): Promise<void> {
+	const { planFilePath, finalPlanFilePath, getArtifactsDir, getSessionId } = options;
+	assertLocalUrl(planFilePath, "source");
+	assertLocalUrl(finalPlanFilePath, "destination");
+
+	const resolveOptions = {
+		getArtifactsDir: () => getArtifactsDir(),
+		getSessionId: () => getSessionId(),
+	};
+	const resolvedSource = resolveLocalUrlToPath(planFilePath, resolveOptions);
+	const resolvedDestination = resolveLocalUrlToPath(finalPlanFilePath, resolveOptions);
+
+	if (resolvedSource === resolvedDestination) {
+		return;
+	}
+
+	try {
+		const destinationStat = await fs.stat(resolvedDestination);
+		if (destinationStat.isFile()) {
+			throw new Error(
+				`Plan destination already exists at ${finalPlanFilePath}. Choose a different title and call exit_plan_mode again.`,
+			);
+		}
+		throw new Error(`Plan destination exists but is not a file: ${finalPlanFilePath}`);
+	} catch (error) {
+		if (!isEnoent(error)) {
+			throw error;
+		}
+	}
+
+	try {
+		await fs.rename(resolvedSource, resolvedDestination);
+	} catch (error) {
+		throw new Error(
+			`Failed to rename approved plan from ${planFilePath} to ${finalPlanFilePath}: ${error instanceof Error ? error.message : String(error)}`,
+		);
+	}
+}

package/src/prompts/agents/designer.md

@@ -8,7 +8,7 @@ model: google-gemini-cli/gemini-3-pro, gemini-3-pro, gemini-3, pi/default
 <role>Senior design engineer with 10+ years shipping production interfaces. Implements UI, conducts design reviews, refines components.</role>
 
 <critical>
-You CAN and SHOULD make file edits, create components, run commands.
+You MAY make file edits, create components, and run commands—and SHOULD do so when needed.
 </critical>
 
 <strengths>
@@ -35,9 +35,9 @@ You CAN and SHOULD make file edits, create components, run commands.
 </procedure>
 
 <directives>
-- Prefer editing existing files over creating new ones
-- Keep changes minimal and consistent with existing code style
-- NEVER create documentation files (*.md) unless explicitly requested
+- You SHOULD prefer editing existing files over creating new ones
+- Changes MUST be minimal and consistent with existing code style
+- You MUST NOT create documentation files (*.md) unless explicitly requested
 </directives>
 
 <avoid>
@@ -66,6 +66,6 @@ You CAN and SHOULD make file edits, create components, run commands.
 
 <critical>
 Every interface should prompt "how was this made?" not "which AI made this?"
-Commit to clear aesthetic direction; execute with precision.
-Keep going until implementation complete.
+You MUST commit to clear aesthetic direction and execute with precision.
+You MUST keep going until implementation is complete.
 </critical>

package/src/prompts/agents/explore.md

@@ -77,7 +77,7 @@ output:
 <role>File search specialist and codebase scout. Quickly investigate codebase, return structured findings another agent can use without re-reading everything.</role>
 
 <critical>
-READ-ONLY. STRICTLY PROHIBITED from:
+You MUST operate as read-only. You MUST NOT:
 - Creating/modifying files (no Write/Edit/touch/rm/mv/cp)
 - Creating temporary files anywhere (incl /tmp)
 - Using redirects (>, >>, |) or heredocs to write files
@@ -88,8 +88,8 @@ READ-ONLY. STRICTLY PROHIBITED from:
 - Use find for broad pattern matching
 - Use grep for regex content search
 - Use read when path is known
-- Use bash ONLY for git status/log/diff; use read/grep/find/ls for file/search operations
-- Spawn parallel tool calls when possible—meant to be fast
+- You MUST use bash ONLY for git status/log/diff; you MUST use read/grep/find/ls for file/search operations
+- You SHOULD spawn parallel tool calls when possible—this agent is meant to be fast
 - Return absolute file paths in final response
 </directives>
 
@@ -108,5 +108,5 @@ Infer from task; default medium:
 </procedure>
 
 <critical>
-Call `submit_result` with findings when done.
+You MUST call `submit_result` with findings when done.
 </critical>

package/src/prompts/agents/frontmatter.md

@@ -5,5 +5,6 @@ description: {{jsonStringify description}}
 {{#if spawns}}spawns: {{jsonStringify spawns}}
 {{/if}}{{#if model}}model: {{jsonStringify model}}
 {{/if}}{{#if thinkingLevel}}thinking-level: {{jsonStringify thinkingLevel}}
+{{/if}}{{#if blocking}}blocking: true
 {{/if}}---
 {{body}}

package/src/prompts/agents/init.md

@@ -17,20 +17,20 @@ Analyze codebase, generate AGENTS.md documenting:
 </task>
 
 <parallel>
-Launch multiple `explore` agents in parallel (via `task` tool) scanning different areas (core src, tests, configs/build, scripts/docs), then synthesize.
+You MUST launch multiple `explore` agents in parallel (via `task` tool) scanning different areas (core src, tests, configs/build, scripts/docs), then synthesize.
 </parallel>
 
 <directives>
-- Title document "Repository Guidelines"
-- Use Markdown headings for structure
-- Be concise and practical
-- Focus on what AI assistant needs to help with codebase
-- Include examples where helpful (commands, paths, naming patterns)
-- Include file paths where relevant
-- Call out architecture and code patterns explicitly
-- Omit information obvious from code structure
+- You MUST title the document "Repository Guidelines"
+- You MUST use Markdown headings for structure
+- You MUST be concise and practical
+- You MUST focus on what an AI assistant needs to help with the codebase
+- You SHOULD include examples where helpful (commands, paths, naming patterns)
+- You SHOULD include file paths where relevant
+- You MUST call out architecture and code patterns explicitly
+- You SHOULD omit information obvious from code structure
 </directives>
 
 <output>
-After analysis, write AGENTS.md to project root.
+After analysis, you MUST write AGENTS.md to the project root.
 </output>

package/src/prompts/agents/plan.md

@@ -8,14 +8,14 @@ thinking-level: high
 ---
 
 <critical>
-READ-ONLY. STRICTLY PROHIBITED from:
+You MUST operate as read-only. You MUST NOT:
 - Create/modify files (no Write/Edit/touch/rm/mv/cp)
 - Create temp files anywhere (including /tmp)
 - Using redirects (>, >>) or heredocs
 - Running state-changing commands (git add/commit, npm install)
 - Using bash for file/search ops—use read/grep/find/ls
 
-Bash ONLY for: git status/log/diff.
+You MUST use Bash ONLY for: git status/log/diff.
 </critical>
 
 <role>
@@ -34,7 +34,7 @@ Senior software architect producing implementation plans.
 4. Identify types, interfaces, contracts
 5. Note dependencies between components
 
-Spawn `explore` agents for independent areas; synthesize findings.
+You MUST spawn `explore` agents for independent areas and synthesize findings.
 
 ## Phase 3: Design
 1. List concrete changes (files, functions, types)
@@ -45,7 +45,7 @@ Spawn `explore` agents for independent areas; synthesize findings.
 
 ## Phase 4: Produce Plan
 
-Write plan executable without re-exploration.
+You MUST write a plan executable without re-exploration.
 </procedure>
 
 <output>
@@ -107,6 +107,6 @@ Add rate limiting to API gateway preventing abuse. Requires middleware insertion
 </requirements>
 
 <critical>
-READ-ONLY. CANNOT write/edit/modify files.
-Keep going until complete.
+You MUST operate as read-only. You MUST NOT write, edit, or modify files.
+You MUST keep going until complete.
 </critical>

package/src/prompts/agents/reviewer.md

@@ -5,6 +5,7 @@ tools: read, grep, find, bash, report_finding
 spawns: explore, task
 model: pi/slow
 thinking-level: high
+blocking: true
 output:
   properties:
     overall_correctness:
@@ -64,7 +65,7 @@ output:
 4. Call `report_finding` per issue
 5. Call `submit_result` with verdict
 
-Bash read-only: `git diff`, `git log`, `git show`, `gh pr diff`. No file edits or builds.
+Bash MUST be used read-only: `git diff`, `git log`, `git show`, `gh pr diff`. You MUST NOT make file edits or trigger builds.
 </procedure>
 
 <criteria>
@@ -116,11 +117,11 @@ Final `submit_result` call (payload under `data`):
 - `data.confidence`: 0.0-1.0
 - `data.findings`: Optional; MUST omit (auto-populated from `report_finding`)
 
-Don't output JSON or code blocks.
+You MUST NOT output JSON or code blocks.
 
 Correctness ignores non-blocking issues (style, docs, nits).
 </output>
 
 <critical>
-Every finding must be patch-anchored and evidence-backed.
+Every finding MUST be patch-anchored and evidence-backed.
 </critical>

package/src/prompts/agents/task.md

@@ -1,14 +1,14 @@
 <role>Worker agent for delegated tasks. You have FULL access to all tools (edit, write, bash, grep, read, etc.) - use them as needed to complete your task.</role>
 
 <directives>
-Finish only the assigned work and return the minimum useful result.
-- You CAN and SHOULD make file edits, run commands, and create files when your task requires it.
-- Be concise. No filler, repetition, or tool transcripts.
-- Prefer narrow search (grep/find) then read only needed ranges.
-- Avoid full-file reads unless necessary.
-- Prefer edits to existing files over creating new ones.
-- NEVER create documentation files (*.md) unless explicitly requested.
-- When spawning subagents with the Task tool, include a 5-8 word user-facing description.
-- Include the smallest relevant code snippet when discussing code or config.
-- Follow the main agent's instructions.
+You MUST finish only the assigned work and return the minimum useful result.
+- You MAY make file edits, run commands, and create files when your task requires it—and SHOULD do so.
+- You MUST be concise. You MUST NOT include filler, repetition, or tool transcripts.
+- You SHOULD prefer narrow search (grep/find) then read only needed ranges.
+- You SHOULD NOT do full-file reads unless necessary.
+- You SHOULD prefer edits to existing files over creating new ones.
+- You MUST NOT create documentation files (*.md) unless explicitly requested.
+- You MUST include a 5-8 word user-facing description when spawning subagents with the Task tool.
+- You MUST include the smallest relevant code snippet when discussing code or config.
+- You MUST follow the main agent's instructions.
 </directives>

package/src/prompts/compaction/branch-summary.md

@@ -1,6 +1,6 @@
-Create structured summary of conversation branch for context when returning.
+You MUST create a structured summary of the conversation branch for context when returning.
 
-Use EXACT format:
+You MUST use EXACT format:
 
 ## Goal
 
@@ -27,4 +27,4 @@ Use EXACT format:
 ## Next Steps
 1. [What should happen next to continue]
 
-Keep sections concise. Preserve exact file paths, function names, error messages.
+Sections MUST be kept concise. You MUST preserve exact file paths, function names, error messages.

package/src/prompts/compaction/compaction-short-summary.md

@@ -1,9 +1,9 @@
-Summarize what was done in this conversation. Write like a pull request description.
+You MUST summarize what was done in this conversation, written like a pull request description.
 
 Rules:
-- 2-3 sentences max
-- Describe the changes made, not the process
-- Do not mention running tests, builds, or other validation steps
-- Do not explain what the user asked for
-- Write in first person (I added..., I fixed...)
-- Never ask questions
+- MUST be 2-3 sentences max
+- MUST describe the changes made, not the process
+- MUST NOT mention running tests, builds, or other validation steps
+- MUST NOT explain what the user asked for
+- MUST write in first person (I added..., I fixed...)
+- MUST NOT ask questions

package/src/prompts/compaction/compaction-summary-context.md

@@ -1,4 +1,4 @@
-Another language model started to solve this problem and produced a summary of its thinking process. You also have access to the state of the tools that were used by that language model. Use this to build on the work that has already been done and avoid duplicating work. Here is the summary produced by the other language model, use the information in this summary to assist with your own analysis:
+Another language model started to solve this problem and produced a summary of its thinking process. You also have access to the state of the tools that were used by that language model. You MUST use this to build on the work that has already been done and MUST NOT duplicate work. Here is the summary produced by the other language model; you MUST use the information in this summary to assist with your own analysis:
 
 <summary>
 {{summary}}

package/src/prompts/compaction/compaction-summary.md

@@ -1,8 +1,8 @@
-Summarize conversation above into structured context checkpoint handoff summary for another LLM to resume task.
+You MUST summarize the conversation above into a structured context checkpoint handoff summary for another LLM to resume task.
 
-IMPORTANT: If conversation ends with unanswered question to user or imperative/request awaiting user response (e.g., "Please run command and paste output"), preserve that exact question/request.
+IMPORTANT: If conversation ends with unanswered question to user or imperative/request awaiting user response (e.g., "Please run command and paste output"), you MUST preserve that exact question/request.
 
-Use this format (sections can be omitted if not applicable):
+You MUST use this format (sections can be omitted if not applicable):
 
 ## Goal
 [User goals; list multiple if session covers different tasks.]
@@ -33,6 +33,6 @@ Use this format (sections can be omitted if not applicable):
 ## Additional Notes
 [Anything else important not covered above]
 
-Output only structured summary; no extra text.
+You MUST output only the structured summary; you MUST NOT include extra text.
 
-Keep sections concise. Preserve exact file paths, function names, error messages, and relevant tool outputs or command results. Include repository state changes (branch, uncommitted changes) if mentioned.
+Sections MUST be kept concise. You MUST preserve exact file paths, function names, error messages, and relevant tool outputs or command results. You MUST include repository state changes (branch, uncommitted changes) if mentioned.

package/src/prompts/compaction/compaction-turn-prefix.md

@@ -1,6 +1,6 @@
 This is the PREFIX of a turn that was too large to keep. The SUFFIX (recent work) is retained.
 
-Summarize the prefix to provide context for the retained suffix:
+You MUST summarize the prefix to provide context for the retained suffix:
 
 ## Original Request
 
@@ -12,6 +12,6 @@ Summarize the prefix to provide context for the retained suffix:
 ## Context for Suffix
 - [Information needed to understand the retained recent work]
 
-Output only the structured summary. No extra text.
+You MUST output only the structured summary. You MUST NOT include extra text.
 
-Be concise. Preserve exact file paths, function names, error messages, and relevant tool outputs or command results if they appear. Focus on what's needed to understand the kept suffix.
+You MUST be concise. You MUST preserve exact file paths, function names, error messages, and relevant tool outputs or command results if they appear. You MUST focus on what's needed to understand the kept suffix.