@oh-my-pi/pi-coding-agent 14.9.9 → 15.0.1

package/src/prompts/tools/hashline.md

@@ -1,162 +1,150 @@
 Your patch language is a compact, line-anchored edit format.
 
-A patch contains one or more file sections. The first non-blank line of every edit section **MUST** be `@@ PATH`.
+A patch contains one or more file sections. The first non-blank line of every edit section MUST be `@@ PATH`.
 Operations reference lines in the file by their line number and hash, called "Anchors", e.g. `5th`, `123ab`.
-You **MUST** copy them verbatim from the latest output for the file you're editing.
+You MUST copy them verbatim from the latest output for the file you're editing.
 
-Purely textual format. The tool has NO awareness of language, indentation, brackets, fences, or table widths. Emit valid syntax in replacements/insertions.
+Purely textual format. The tool has NO awareness of language, indentation, brackets, fences, or table widths. You MUST emit valid syntax in replacements/insertions.
 
 <ops>
 @@ PATH          header: subsequent ops apply to PATH
+Each op line is ONE of:
 + ANCHOR         insert lines AFTER  the anchored line (or EOF); payload follows as `{{hsep}}TEXT` lines
 < ANCHOR         insert lines BEFORE the anchored line (or BOF); payload follows as `{{hsep}}TEXT` lines
 - A..B           delete the line range (inclusive).
 = A..B           replace the range with payload `{{hsep}}TEXT` lines, or with one blank line if no payload follows.
 </ops>
 
+<format-reminder>
+Op lines carry no content — payload goes on the next line.
+
+WRONG: + 5pg| some code
+RIGHT: + 5pg
+       {{hsep}} some code
+
+A single `+`/`<`/`=` op accepts MANY `{{hsep}}` payload lines. To insert N consecutive lines, write ONE op followed by N payload lines — NEVER N ops with one payload each.
+
+WRONG (one op per inserted line, with fabricated anchors):
+  + 5pg
+  {{hsep}}first new line
+  + 6xx    ← FABRICATED
+  {{hsep}}second new line
+
+RIGHT (one op, many payload lines):
+  + 5pg
+  {{hsep}}first new line
+  {{hsep}}second new line
+</format-reminder>
+
 <rules>
-- Every line of inserted/replacement content **MUST** be emitted as a payload line starting with `{{hsep}}`.
-- `{{hsep}}` is syntax, not content. The inserted text begins after the first `{{hsep}}`; use a bare `{{hsep}}` to insert a blank line.
-- Payload is verbatim — don't escape unicode (write `—`, not `\u2014`).
-- `< A` inserts before line A; `+ A` inserts after line A. `< BOF` / `+ BOF` both prepend; `< EOF` / `+ EOF` both append.
-- `= A..B` replaces the inclusive range with the following payload lines. `= A..B` with no payload blanks the range to a single empty line.
-- `- A..B` deletes the inclusive range; `A..A` for one line.
-- **Choose a self-contained syntactic unit first.** If the change touches part of a multiline call, destructuring assignment, control-flow header, wrapper, or other construct, widen the range to include the whole construct before optimizing for size.
-- Only after the range is self-contained, pick the smallest op for the change: pure addition → `+`/`<`; pure deletion → `-`; `= A..B` ONLY when content inside `A..B` is actually being modified or removed.
+- Every payload line MUST start with `{{hsep}}`.
+- Payload is verbatim — NEVER escape unicode.
+- **Payload is only what's NEW relative to your range:**
+  - `=` replaces inside; NEVER include lines outside.
+  - `+`/`<` adds at the anchor; NEVER repeat line A or neighbors.
+  - Payload matching nearby content duplicates — drop it or widen.
+- **Pick a self-contained unit first.** Touching a multiline construct? Widen to the whole thing.
+- Then smallest op: add → `+`/`<`; delete → `-`; `=` ONLY when modifying inside.
 </rules>
 
 <brace-shapes>
-When your edit involves brace boundaries (`{` / `}`), prefer these shapes:
-- **Whole block replace/delete**: pick the range so it spans both halves of the brace pair — start on the line that ends with `{`, end on the matching `}`. For pure removal use `-` with empty payload; for replacement, the payload's first line ends with `{` and last line is the matching `}`.
-- **Signature-only edit**: if you are only changing the line that ends with `{` (function signature, control statement, etc.), use a one-line `=` on that opener; the body and matching `}` are untouched and stay outside the range.
-- **Insert inside a block**: anchor on the opener (`+ ANCHOR` after the `{` line) or just above the closer (`+ ANCHOR` after the last interior line); emit only the new interior lines. Do not include the surrounding `{` or `}` in the payload — they're already there.
-- **Range ending on `}`**: only end on `}` when that `}` is itself part of what you're changing. The line at B+1 should be blank, an opener (next block), or a signature — not another `}`. Otherwise extend B past the closer or stop one line earlier.
+When braces bound your edit, you SHOULD prefer these shapes:
+- **Whole block**: range spans `{` through matching `}`.
+- **Signature only**: one-line `=` on the opener; body untouched.
+- **Insert inside**: anchor on `{` or last interior line; NEVER repeat the braces.
+- **End on `}`**: only when that `}` is part of the change. Otherwise extend or stop earlier.
 </brace-shapes>
 
 <common-failures>
-- **Do not replay the line past your range.** For `= A..B`, never end the payload with content that already exists at B+1. Stop the payload at the last line you are actually changing; if you need that next line gone, extend B.
-- **Do not duplicate chunks inside one payload.** When emitting a long `=` payload, never paste the same multi-line block twice. If you catch yourself re-emitting an earlier run of lines, stop and rewrite the op.
-- **Anchor only inside the visible region.** If the read output around your `=`/`-` end anchor is truncated (you cannot see the line at B+1), issue a fresh `read` before editing — anchoring blind drops or duplicates the boundary line.
-- **Prefer the narrowest self-contained edit.** Once your range cleanly contains the construct you are changing, a `+`/`<` insert plus a small `-` delete is almost always clearer and safer than a single wide `= A..B` that re-emits unchanged context.
-- **Anchors always reference the file as you last read it.** When stacking multiple `+`/`<`/`-`/`=` ops in one patch, do **NOT** mentally shift line numbers to account for prior ops in the same patch. Every op resolves against the original line numbering.
+- **NEVER replay past your range.** Stop before B+1; extend B if it must go.
+- **NEVER duplicate chunks inside one payload.** Caught re-emitting? Rewrite.
+- **Anchor only inside the visible region.** B+1 truncated? Re-`read` first.
+- **You SHOULD prefer the narrowest self-contained edit.** Small `+`/`-` beats wide `=`.
+- **Anchors reference the file as last read.** NEVER shift for prior ops.
+- **One `+`/`<` op per block, NOT per line.** N lines = ONE op, N payloads. Collapse adjacent ops.
+- **NEVER fabricate anchor hashes.** Missing? Re-`read`.
 </common-failures>
 
-<case file="a.ts">
+<case file="mod.ts">
 {{hline 1 "const DEF = \"guest\";"}}
-{{hline 2 ""}}
-{{hline 3 "export function label(name) {"}}
-{{hline 4 "\tconst clean = name || DEF;"}}
-{{hline 5 "\treturn clean.trim();"}}
-{{hline 6 "}"}}
-</case>
-
-<case file="b.ts">
-{{hline 1 "const {"}}
-{{hline 2 "\tevents,"}}
-{{hline 3 "\tresponse,"}}
-{{hline 4 "\trequestId,"}}
-{{hline 5 "} = await getStreamResponse("}}
-{{hline 6 "\trequest,"}}
-{{hline 7 "\tsignal,"}}
-{{hline 8 ");"}}
-{{hline 9 "await notify(requestId);"}}
+{{hline 2 "export function label(name) {"}}
+{{hline 3 "\treturn ["}}
+{{hline 4 "\t\tname?.trim() || DEF,"}}
+{{hline 5 "\t\t\" • \","}}
+{{hline 6 "\t].join(\"\");"}}
+{{hline 7 "}"}}
 </case>
 
 <examples>
-# Replace one line (preserve the leading tab from the original)
-@@ a.ts
-= {{hrefr 5}}..{{hrefr 5}}
-{{hsep}}	return clean.trim().toUpperCase();
-
-# Replace a contiguous range with multiple lines
-@@ a.ts
-= {{hrefr 4}}..{{hrefr 5}}
-{{hsep}}	const clean = (name || DEF).trim();
-{{hsep}}	return clean.length === 0 ? DEF : clean.toUpperCase();
-
-# Replace a full multiline destructuring/call statement
-@@ b.ts
-= {{hrefr 1}}..{{hrefr 8}}
-{{hsep}}const {
-{{hsep}}	events,
-{{hsep}}	response,
-{{hsep}}	requestId,
-{{hsep}}} = await getStreamResponse(
-{{hsep}}	request,
-{{hsep}}	signal,
-{{hsep}}	onEvent,
-{{hsep}});
-
-# Insert BEFORE a line
-@@ a.ts
+# Replace one line (the payload must re-emit the original indentation)
+@@ mod.ts
+= {{hrefr 4}}..{{hrefr 4}}
+{{hsep}}		name?.trim().toUpperCase() || DEF,
+
+# Replace a full multiline statement (widen to a self-contained boundary)
+@@ mod.ts
+= {{hrefr 3}}..{{hrefr 6}}
+{{hsep}}	return [
+{{hsep}}		name?.trim() || DEF,
+{{hsep}}		"·",
+{{hsep}}		" • ",
+{{hsep}}	].join("");
+
+# Insert AFTER/BEFORE a line
+@@ mod.ts
++ {{hrefr 3}}
+{{hsep}}		"·",
 < {{hrefr 5}}
-{{hsep}}	const debug = false;
-
-# Insert AFTER a line
-@@ a.ts
-+ {{hrefr 4}}
-{{hsep}}	if (clean.length === 0) return DEF;
+{{hsep}}		"·",
 
-# Append to end of file
-@@ a.ts
+# Append to file
+@@ mod.ts
 + EOF
 {{hsep}}export const done = true;
 
-# Delete a single line
-@@ a.ts
-- {{hrefr 2}}..{{hrefr 2}}
+# Delete a line
+@@ mod.ts
+- {{hrefr 5}}..{{hrefr 5}}
 
-# Blank a line in place (no payload required)
-@@ a.ts
-= {{hrefr 2}}..{{hrefr 2}}
+# Blank a line (replace with LF)
+@@ mod.ts
+= {{hrefr 5}}..{{hrefr 5}}
 </examples>
 
 <anti-pattern>
-# WRONG — replaces 5 lines just to add one. Use `+` at the boundary instead.
-@@ a.ts
-= {{hrefr 1}}..{{hrefr 5}}
+# WRONG — replaces 3 lines just to add one.
+@@ mod.ts
+= {{hrefr 1}}..{{hrefr 3}}
 {{hsep}}const DEF = "guest";
 {{hsep}}const DEBUG = false;
-{{hsep}}
 {{hsep}}export function label(name) {
-{{hsep}}	const clean = name || DEF;
-{{hsep}}	return clean.trim();
-
+{{hsep}}	return [
 # RIGHT — same effect, one-line insert
-@@ a.ts
+@@ mod.ts
 + {{hrefr 1}}
 {{hsep}}const DEBUG = false;
 
-# WRONG — continuation-fragment payload from the middle of a larger statement.
-@@ b.ts
-= {{hrefr 5}}..{{hrefr 7}}
-{{hsep}}} = await getStreamResponse(
-{{hsep}}	request,
-{{hsep}}	signal,
-{{hsep}}	onEvent,
-
-# RIGHT — widen to the full statement so the payload starts at a self-contained boundary.
-@@ b.ts
-= {{hrefr 1}}..{{hrefr 8}}
-{{hsep}}const {
-{{hsep}}	events,
-{{hsep}}	response,
-{{hsep}}	requestId,
-{{hsep}}} = await getStreamResponse(
-{{hsep}}	request,
-{{hsep}}	signal,
-{{hsep}}	onEvent,
-{{hsep}});
-
-If your replacement payload would render with even one unchanged line in the diff, or if the first or last payload line is only a continuation fragment from a larger construct (`} =`, `);`, `,`, `.method(`), you have the wrong op or range. Stop and widen to a self-contained boundary before minimizing the edit.
+# WRONG — replace from the middle of a larger statement (error-prone)
+@@ mod.ts
+= {{hrefr 4}}..{{hrefr 5}}
+{{hsep}}		name?.trim() || DEF,
+{{hsep}}		"·",
+{{hsep}}		" • ",
+# RIGHT — widen to the full statement
+@@ mod.ts
+= {{hrefr 3}}..{{hrefr 6}}
+{{hsep}}	return [
+{{hsep}}		name?.trim() || DEF,
+{{hsep}}		"·",
+{{hsep}}		" • ",
+{{hsep}}	].join("");
 </anti-pattern>
 
 <critical>
-- Always copy anchors exactly from tool output, but **NEVER** include line content after the `{{hsep}}` separator in the op line.
-- Every inserted/replacement content line **MUST** start with `{{hsep}}`; raw content lines are invalid.
-- Do not write unified diff syntax (`@@ -X,Y +X,Y @@`, `-OLD`, `+NEW`). The header is `@@ PATH`; line ops are `<`/`+`/`-`/`=`.
-- `= A..B` deletes the range; payload is what's written. If a payload edge line already exists immediately outside `A..B`, widen the range to cover it — otherwise it duplicates.
-- Multiple ops in one patch are cheap. Prefer two narrow ops over one wide `=`.
-  - Before choosing a `= A..B` range, mentally delete lines A through B. If that would split an unclosed bracket, paren, brace, or string/template from a line above A, or orphan a closing delimiter that belongs to an opener inside the range, you are bisecting a syntactic construct. Widen the range to a self-contained boundary, or use `+`/`-` instead.
-  - `= A..B` removes the range as a unit; the lines immediately outside it remain. If those outside lines form a wrapper (`try {`, `catch`, `if`, `else`, loop delimiters) you do not intend to delete, your payload is inserted inside that wrapper. Make sure the payload remains valid and preserves required behavior like error handling. If you need to change the wrapper itself, include it in the range and reproduce it.
+- Copy anchors verbatim (line number + 2-char hash); NEVER include the `|TEXT` body.
+- Every payload line MUST start with `{{hsep}}`; raw content is invalid.
+- NEVER write unified diff syntax. Header is `@@ PATH`; ops are `<`/`+`/`-`/`=`.
+- `= A..B` deletes the range; payload is what's written. Edge line matches just outside? Widen, or it duplicates.
+- Multiple ops are cheap. SHOULD prefer two narrow ops over one wide `=`.
+  - Before `= A..B`, mentally delete A..B. Splits an unclosed bracket/brace/string from above, or orphans a closer inside? You're bisecting a construct.
 </critical>

package/src/prompts/tools/image-gen.md

@@ -1,7 +1,7 @@
 Generates or edits images.
 
 <instructions>
-- You **MUST** provide a single detailed `subject` prompt for image generation or editing.
-- When using multiple `input`, you **SHOULD** describe each image's role directly in `subject`, e.g. `Image 1` for composition reference, `Image 2` for lighting reference, `Image 3` for background.
-- For text: you **SHOULD** add "sharp, legible, correctly spelled" for important text; keep text short
+- You MUST provide a single detailed `subject` prompt for image generation or editing.
+- When using multiple `input`, you SHOULD describe each image's role directly in `subject`, e.g. `Image 1` for composition reference, `Image 2` for lighting reference, `Image 3` for background.
+- For text: you SHOULD add "sharp, legible, correctly spelled" for important text; keep text short
 </instructions>

package/src/prompts/tools/irc.md

@@ -9,7 +9,7 @@ Sends short text messages to other live agents in this process and receives thei
 </instruction>
 
 <when_to_use>
-You **SHOULD** reach for `irc` proactively when continuing alone is wasteful or wrong. When in doubt, prefer messaging.
+You SHOULD reach for `irc` proactively when continuing alone is wasteful or wrong. When in doubt, prefer messaging.
 - **Unexpected state.** You hit something the original task did not describe — a missing file, a config that contradicts the assignment, an API behaving differently than you were told, a tool failing in a way that suggests the spec is wrong. DM `0-Main` (or the spawning agent) for guidance instead of guessing.
 - **Blocked by another agent.** A peer holds the file/branch/resource you need, has already started the change you are about to make, or owns a decision you depend on. DM that peer (or broadcast to discover who) before duplicating or stepping on work.
 - **Decision points outside your scope.** A genuine fork in the road that the assignment did not pre-decide (e.g. which of two viable APIs to use, whether to refactor adjacent code). Ask the requester rather than picking unilaterally.

package/src/prompts/tools/lsp.md

@@ -36,7 +36,7 @@ Interacts with Language Server Protocol servers for code intelligence.
 </caution>
 
 <critical>
-- You **MUST** use `lsp` for symbol-aware operations (rename, find references, go to definition/implementation, code actions) whenever a language server is available — it is safer and more accurate than text-based alternatives.
-- You **MUST NOT** perform cross-file renames with `ast_edit`, `sed`, `rsed`, or manual edits when `lsp` `rename` can do it. Text-based renames miss shadowing, re-exports, and usages in other files.
+- You MUST use `lsp` for symbol-aware operations (rename, find references, go to definition/implementation, code actions) whenever a language server is available — it is safer and more accurate than text-based alternatives.
+- You NEVER perform cross-file renames with `ast_edit`, `sed`, `rsed`, or manual edits when `lsp` `rename` can do it. Text-based renames miss shadowing, re-exports, and usages in other files.
 - Prefer `lsp` `code_actions` for imports, quick-fixes, and refactors the language server already knows how to apply.
 </critical>

package/src/prompts/tools/patch.md

@@ -42,12 +42,12 @@ Returns success/failure; on failure, error message indicates:
 </output>
 
 <critical>
-- You **MUST** read the target file before editing
-- You **MUST** copy anchors and context lines verbatim (including whitespace)
-- You **MUST NOT** use anchors as comments (no line numbers, location labels, placeholders like `@@ @@`)
-- You **MUST NOT** place new lines outside the intended block
-- If edit fails or breaks structure, you **MUST** re-read the file and produce a new patch from current content — you **MUST NOT** retry the same diff
-- **NEVER** use edit to fix indentation, whitespace, or reformat code. Formatting is a single command run once at the end (`bun fmt`, `cargo fmt`, `prettier —write`, etc.)—not N individual edits. If you see inconsistent indentation after an edit, leave it; the formatter will fix all of it in one pass.
+- You MUST read the target file before editing
+- You MUST copy anchors and context lines verbatim (including whitespace)
+- You NEVER use anchors as comments (no line numbers, location labels, placeholders like `@@ @@`)
+- You NEVER place new lines outside the intended block
+- If edit fails or breaks structure, you MUST re-read the file and produce a new patch from current content — you NEVER retry the same diff
+- NEVER use edit to fix indentation, whitespace, or reformat code. Formatting is a single command run once at the end (`bun fmt`, `cargo fmt`, `prettier —write`, etc.)—not N individual edits. If you see inconsistent indentation after an edit, leave it; the formatter will fix all of it in one pass.
 </critical>
 
 <examples>

package/src/prompts/tools/read.md

@@ -2,8 +2,8 @@ Reads the content at the specified path or URL.
 
 <instruction>
 The `read` tool is multi-purpose and more capable than it looks — inspects files, directories, archives, SQLite databases, images, documents (PDF/DOCX/PPTX/XLSX/RTF/EPUB/ipynb), **and URLs**.
-- You **MUST** parallelize reads when exploring related files
-- For URLs, `read` fetches the page and returns clean extracted text/markdown by default (reader-mode). It handles HTML pages, GitHub issues/PRs, Stack Overflow, Wikipedia, Reddit, NPM, arXiv, RSS/Atom, JSON endpoints, PDFs, etc. You **SHOULD** reach for `read` — not a browser/puppeteer tool — for fetching and inspecting web content.
+- You MUST parallelize reads when exploring related files
+- For URLs, `read` fetches the page and returns clean extracted text/markdown by default (reader-mode). It handles HTML pages, GitHub issues/PRs, Stack Overflow, Wikipedia, Reddit, NPM, arXiv, RSS/Atom, JSON endpoints, PDFs, etc. You SHOULD reach for `read` — not a browser/puppeteer tool — for fetching and inspecting web content.
 
 ## Parameters
 - `path` — file path or URL (required). Append `:<sel>` for line ranges or raw mode (for example `src/foo.ts:50-200` or `src/foo.ts:raw`).
@@ -17,6 +17,7 @@ The `read` tool is multi-purpose and more capable than it looks — inspects fil
 |`:50-200`|Read lines 50-200|
 |`:50+150`|Read 150 lines starting at line 50|
 |`:20+1`|Read exactly one line|
+|`:5-16,960-973`|Read multiple ranges in one call (comma-separated; ranges sort and merge automatically)|
 |`:raw`|Read verbatim text without anchors or summarization|
 |`:conflicts`|Return a one-line-per-block index of every merge conflict in the file|
 
@@ -55,9 +56,9 @@ Extracts content from web pages, GitHub issues/PRs, Stack Overflow, Wikipedia, R
 </instruction>
 
 <critical>
-- You **MUST** use `read` for every file, directory, archive, and URL read. `cat`, `head`, `tail`, `less`, `more`, `ls`, `tar`, `unzip`, `curl`, and `wget` are **FORBIDDEN** for inspection — any such Bash call is a bug, regardless of how short or convenient it looks.
-- You **MUST** prefer `read` over a browser/puppeteer tool for fetching URL content; only use a browser if `read` fails to deliver reasonable content.
-- You **MUST** always include the `path` parameter — never call `read` with an empty argument object `{}`.
-- For specific line ranges, append the selector to `path` (e.g. `path="src/foo.ts:50-200"`, `path="src/foo.ts:50+150"`) — do **NOT** reach for `sed -n`, `awk NR`, or `head`/`tail` pipelines.
-- You **MAY** use path suffix selectors with URL reads; the tool paginates cached fetched output.
+- You MUST use `read` for every file, directory, archive, and URL read. `cat`, `head`, `tail`, `less`, `more`, `ls`, `tar`, `unzip`, `curl`, and `wget` are **FORBIDDEN** for inspection — any such Bash call is a bug, regardless of how short or convenient it looks.
+- You MUST prefer `read` over a browser/puppeteer tool for fetching URL content; only use a browser if `read` fails to deliver reasonable content.
+- You MUST always include the `path` parameter — never call `read` with an empty argument object `{}`.
+- For specific line ranges, append the selector to `path` (e.g. `path="src/foo.ts:50-200"`, `path="src/foo.ts:50+150"`) — NEVER reach for `sed -n`, `awk NR`, or `head`/`tail` pipelines.
+- You MAY use path suffix selectors with URL reads; the tool paginates cached fetched output.
 </critical>

package/src/prompts/tools/replace.md

@@ -1,10 +1,10 @@
 Performs string replacements in files with fuzzy whitespace matching.
 
 <instruction>
-- Params **MUST** be `{ path, edits }`; `path` is required at the top level and applies to every replacement
-- You **MUST** use the smallest `old_text` that uniquely identifies the change
-- If `old_text` is not unique, you **MUST** expand it with more context or use `all: true` to replace all occurrences
-- You **SHOULD** prefer editing existing files over creating new ones
+- Params MUST be `{ path, edits }`; `path` is required at the top level and applies to every replacement
+- You MUST use the smallest `old_text` that uniquely identifies the change
+- If `old_text` is not unique, you MUST expand it with more context or use `all: true` to replace all occurrences
+- You SHOULD prefer editing existing files over creating new ones
 </instruction>
 
 <output>
@@ -12,7 +12,7 @@ Returns success/failure status. On success, file modified in place with replacem
 </output>
 
 <critical>
-- You **MUST** read the file at least once in the conversation before editing. Tool errors if you attempt edit without reading file first.
+- You MUST read the file at least once in the conversation before editing. Tool errors if you attempt edit without reading file first.
 </critical>
 
 <bash-alternatives>

package/src/prompts/tools/resolve.md

@@ -1,8 +1,9 @@
-Resolves a pending preview action by either applying or discarding it.
+Resolves a pending action by either applying or discarding it.
 - `action` is required:
-  - `"apply"` persists the pending changes.
-  - `"discard"` rejects the pending changes.
-- `reason` is required and must explain why you chose to apply or discard.
+  - `"apply"` persists / submits the pending action.
+  - `"discard"` rejects the pending action.
+- `reason` is required and must briefly explain why you chose to apply or discard.
+- `extra` (optional) is free-form metadata passed to the resolving tool. Schema depends on context:
 
-Only valid when a pending action exists (typically after a preview step).
+Valid whenever a pending action exists — either a preview-style staging (e.g. `ast_edit`) or a long-lived approval gate.
 Call fails with an error when no pending action exists.

package/src/prompts/tools/retain.md

@@ -3,4 +3,4 @@ Store one or more facts in long-term memory for future sessions.
 Use for durable, reusable knowledge: user preferences, project decisions, architectural choices, anything that improves future responses.
 Ephemeral task state does not belong here.
 
-Each item **MUST** be specific and self-contained — include who, what, when, and why. Batch related facts in a single call; they are deduplicated and consolidated.
+Each item MUST be specific and self-contained — include who, what, when, and why. Batch related facts in a single call; they are deduplicated and consolidated.

package/src/prompts/tools/rewind.md

@@ -3,10 +3,10 @@ End an active checkpoint. Rewind context to it, replacing intermediate explorati
 Call immediately after `checkpoint`-started investigative work.
 
 Requirements:
-- `report` is **REQUIRED** and must be concise, factual, and actionable.
+- `report` is REQUIRED and must be concise, factual, and actionable.
 - Include key findings, decisions, and any unresolved risks.
 - Do not include raw scratch logs unless essential.
-- You **MUST** call this before yielding if a checkpoint is active.
+- You MUST call this before yielding if a checkpoint is active.
 
 Behavior:
 - If no checkpoint is active, this tool errors.

package/src/prompts/tools/search.md

@@ -17,8 +17,8 @@ Searches files using powerful regex matching.
 </output>
 
 <critical>
-- You **MUST** use the built-in `search` tool for any content search. Do **NOT** shell out to `grep`, `rg`, `ripgrep`, `ag`, `ack`, `git grep`, `awk`, `sed`-for-search, or any other CLI search via Bash — even for a single match, even "just to check quickly", even piped through other commands.
+- You MUST use the built-in `search` tool for any content search. NEVER shell out to `grep`, `rg`, `ripgrep`, `ag`, `ack`, `git grep`, `awk`, `sed`-for-search, or any other CLI search via Bash — even for a single match, even "just to check quickly", even piped through other commands.
 - Bash `grep`/`rg` loses `.gitignore` semantics, bypasses result limits, and wastes tokens. The `search` tool is faster, structured, and already wired into the workspace — there is no scenario where Bash search is preferable.
 - If you catch yourself typing `grep`, `rg`, or `| grep` in a Bash command, stop and re-issue the lookup through the `search` tool instead.
-- If the search is open-ended, requiring multiple rounds, you **MUST** use the Task tool with the explore subagent instead of chaining `search` calls yourself.
+- If the search is open-ended, requiring multiple rounds, you MUST use the Task tool with the explore subagent instead of chaining `search` calls yourself.
 </critical>

package/src/prompts/tools/ssh.md

@@ -1,7 +1,7 @@
 Runs commands on remote hosts.
 
 <instruction>
-You **MUST** build commands from the reference below
+You MUST build commands from the reference below
 </instruction>
 
 <commands>
@@ -22,7 +22,7 @@ You **MUST** build commands from the reference below
 </commands>
 
 <critical>
-You **MUST** verify the shell type from "Available hosts" and use matching commands.
+You MUST verify the shell type from "Available hosts" and use matching commands.
 </critical>
 
 <examples>

package/src/prompts/tools/task.md

@@ -2,14 +2,20 @@ Launches subagents to parallelize workflows.
 
 {{#if asyncEnabled}}
 - Results are delivered automatically when complete.
-- If genuinely blocked on task completion, wait with `job` using `poll`; otherwise continue with another task when possible.
-- Call `job` with `list: true` to snapshot manager state; pass `poll: [id]` to wait or `cancel: [id]` to stop \u2014 only when inspection or intervention is useful.
+- The tool result lists the assigned task ids (e.g. `0-AuthLoader`) — those are the live agent ids.
+{{#if ircEnabled}}
+- Coordinate with running tasks via `irc` using those ids. `job cancel` terminates a task and **cannot carry a message** — only use it for stalled/abandoned work.
+- If genuinely blocked on completion, wait with `job poll`; otherwise keep working.
+{{else}}
+- If genuinely blocked on completion, wait with `job poll`; otherwise keep working.
+- Use `job list` to snapshot manager state; `cancel: [id]` only to actually stop a stuck task.
+{{/if}}
 {{/if}}
 
 {{#if ircEnabled}}
 Subagents have no conversation history, but they can reach you and their siblings live via the `irc` tool. Front-load every fact, file path, and direction they need in {{#if contextEnabled}}`context` or `assignment`{{else}}each `assignment`{{/if}}.
 {{else}}
-Subagents have no conversation history. Every fact, file path, and direction they need **MUST** be explicit in {{#if contextEnabled}}`context` or `assignment`{{else}}each `assignment`{{/if}}.
+Subagents have no conversation history. Every fact, file path, and direction they need MUST be explicit in {{#if contextEnabled}}`context` or `assignment`{{else}}each `assignment`{{/if}}.
 {{/if}}
 
 <parameters>
@@ -24,8 +30,8 @@ Subagents have no conversation history. Every fact, file path, and direction the
 </parameters>
 
 <rules>
-- **MUST NOT** assign tasks to run project-wide build/test/lint. Caller verifies after the batch.
-- **Subagents do not verify, lint, or format.** Every assignment **MUST** instruct the subagent to skip all gates and formatters. You run them once at the end across the union of changed files — avoids redundant runs and racing formatter passes.
+- NEVER assign tasks to run project-wide build/test/lint. Caller verifies after the batch.
+- **Subagents do not verify, lint, or format.** Every assignment MUST instruct the subagent to skip all gates and formatters. You run them once at the end across the union of changed files — avoids redundant runs and racing formatter passes.
 {{#if ircEnabled}}
 - Each task: ≤3–5 explicit files. Overlapping file sets are tolerable when peers can coordinate via `irc`, but still fan out to a cluster when the scopes are cleanly separable.
 - No globs, no "update all", no package-wide scope.
@@ -52,7 +58,7 @@ Parallel when tasks touch disjoint files or are independent refactors/tests.
 {{#if contextEnabled}}
 <context-fmt>
 # Goal         ← one sentence: what the batch accomplishes
-# Constraints  ← **MUST**/**MUST NOT** rules and session decisions
+# Constraints  ← MUST/NEVER rules and session decisions
 # Contract     ← exact types/signatures if tasks share an interface
 </context-fmt>
 {{/if}}

package/src/prompts/tools/web-search.md

@@ -1,8 +1,8 @@
 Searches the web for up-to-date information beyond Claude's knowledge cutoff.
 
 <instruction>
-- You **SHOULD** prefer primary sources (papers, official docs) and corroborate key claims with multiple sources
-- You **MUST** include links for cited sources in the final response
+- You SHOULD prefer primary sources (papers, official docs) and corroborate key claims with multiple sources
+- You MUST include links for cited sources in the final response
 </instruction>
 
 <caution>

package/src/prompts/tools/write.md

@@ -8,7 +8,7 @@ Creates or overwrites file at specified path.
 </conditions>
 
 <critical>
-- You **SHOULD** use Edit tool for modifying existing files (more precise, preserves formatting)
-- You **MUST NOT** create documentation files (*.md, README) unless explicitly requested
-- You **MUST NOT** use emojis unless requested
+- You SHOULD use Edit tool for modifying existing files (more precise, preserves formatting)
+- You NEVER create documentation files (*.md, README) unless explicitly requested
+- You NEVER use emojis unless requested
 </critical>