scream-code 0.10.8 → 0.10.9

package/dist/{app-D_usIcl7.mjs → app-CwHfTwUZ.mjs}

@@ -7,7 +7,7 @@ import { i as __require, o as __toESM, r as __exportAll, t as __commonJSMin } fr
 import "./suppress-sqlite-warning-C2VB0doZ.mjs";
 import { C as join$1, D as resolve$1, E as relative$1, S as isAbsolute$1, T as parse$7, a as isSupportedFile, b as basename$1, i as ingestFile, r as ingestDirectory, t as multiSearch, w as normalize, x as dirname$2, y as KnowledgeStore } from "./src-BH9W5k24.mjs";
 import { t as require_base64_js } from "./base64-js-DzVmk6Nb.mjs";
-import { a as setLocale, i as getLocale, n as assertScreamHostIdentity, o as t, r as createScreamDefaultHeaders, t as TextInputDialogComponent } from "./text-input-dialog-CiWeHRNJ.mjs";
+import { a as setLocale, i as getLocale, n as assertScreamHostIdentity, o as t, r as createScreamDefaultHeaders, t as TextInputDialogComponent } from "./text-input-dialog-DRUaPOEQ.mjs";
 import { createRequire } from "node:module";
 import { createHash, randomBytes, randomInt, randomUUID } from "node:crypto";
 import * as fs$1 from "node:fs/promises";
@@ -52,7 +52,7 @@ import { AsyncLocalStorage } from "node:async_hooks";
 import { Command, Option } from "commander";
 import { createInterface } from "node:readline/promises";
 import chalk, { chalkStderr } from "chalk";
-import { CombinedAutocompleteProvider, Container, Editor, Image, Input, Key, Markdown, ProcessTerminal, Spacer, TUI, Text, decodeKittyPrintable, deleteAllKittyImages, fuzzyFilter, fuzzyMatch, getCapabilities, getImageDimensions, isKeyRelease, matchesKey, truncateToWidth, visibleWidth, wrapTextWithAnsi } from "@liutod-scream/pi-tui";
+import { CombinedAutocompleteProvider, Container, Editor, Image, Input, Key, Markdown, ProcessTerminal, Spacer, TUI, Text, decodeKittyPrintable, deleteAllKittyImages, fuzzyFilter, fuzzyMatch, getCapabilities, getImageDimensions, isKeyRelease, matchesKey, setTightMode, sliceByColumn, truncateToWidth, visibleWidth, wrapTextWithAnsi } from "@liutod-scream/pi-tui";
 import { highlight, supportsLanguage } from "cli-highlight";
 import { diffWords } from "diff";
 import { gt, valid } from "semver";
@@ -49870,6 +49870,7 @@ async function generate(provider, systemPrompt, tools, history, callbacks, optio
 	const hasText = message.content.some((p) => p.type === "text" && p.text.trim().length > 0);
 	const hasToolCalls = message.toolCalls.length > 0;
 	if (hasThink && !hasText && !hasToolCalls) throw new APIEmptyResponseError(`The API returned a response containing only thinking content without any text or tool calls. This usually indicates the stream was interrupted or the output token budget was exhausted during reasoning. Provider: ${provider.name}, model: ${provider.modelName}. If this persists, reduce reasoning effort or switch to a model with a larger output budget.`);
+	if (!hasText && !hasToolCalls && message.content.some((p) => p.type === "text")) throw new APIEmptyResponseError(`The API returned a response containing only empty or whitespace text. This usually indicates a truncated or malformed stream. Provider: ${provider.name}, model: ${provider.modelName}.`);
 	if (callbacks?.onToolCall !== void 0) for (const toolCall of message.toolCalls) {
 		await throwIfAborted$1(options?.signal, stream);
 		await callbacks.onToolCall(toolCall);
@@ -50801,6 +50802,14 @@ function resolveGlobalLogPath(homeDir) {
 //#endregion
 //#region ../../packages/agent-core/src/utils/tokens.ts
 /**
+* WeakMap cache for per-message token estimates. Messages are immutable once
+* settled (streaming `partial` messages never enter compaction paths), so the
+* cache is safe. Spread copies created by micro-compaction ({ ...msg, content })
+* are new objects → natural cache miss → re-estimated. Original objects retain
+* their cached count, avoiding O(n²) re-scans during compaction detection.
+*/
+const messageTokenCache = /* @__PURE__ */ new WeakMap();
+/**
 * Estimate token count from text using a character-based heuristic.
 *   - ASCII (~4 chars per token)
 *   - CJK and other non-ASCII (~1 char per token)
@@ -50830,12 +50839,15 @@ function estimateTokensForTools(tools) {
 	return total;
 }
 function estimateTokensForMessage(message) {
+	const cached = messageTokenCache.get(message);
+	if (cached !== void 0) return cached;
 	let total = estimateTokens$1(message.role);
 	for (const part of message.content) total += estimateTokensForContentPart(part);
 	if (message.toolCalls !== void 0) for (const call of message.toolCalls) {
 		total += estimateTokens$1(call.name);
 		total += estimateTokens$1(JSON.stringify(call.arguments));
 	}
+	messageTokenCache.set(message, total);
 	return total;
 }
 function estimateTokensForContentPart(part) {
@@ -54165,7 +54177,7 @@ function matchRuleSubjects(ruleArgs, subjects, matchesPositivePattern) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/background/task-list.md
-var task_list_default = "List background tasks and their current status.\n\nUse this tool to discover which background tasks exist and where each one\nstands. It is the entry point for inspecting background work: it returns a\ntask ID, status, command, description, and PID for every task it reports,\nplus the exit code and stop reason for tasks that have already finished.\n\nGuidelines:\n\n- After a context compaction, or whenever you are unsure which background\n  tasks are running or what their task IDs are, call this tool to\n  re-enumerate them instead of guessing a task ID.\n- Prefer the default `active_only=true`, which lists only non-terminal tasks.\n  Pass `active_only=false` only when you specifically need to see tasks that\n  have already finished. With `active_only=false` the result may also include\n  `lost` tasks — tasks left over from a previous process that can no longer be\n  inspected or controlled; treat them as already terminated.\n- `limit` caps how many tasks are returned. It accepts a value between 1 and\n  100 and defaults to 20 when omitted.\n- This tool only lists tasks; it does not return their output. Use it first\n  to locate the task ID you need, then call `TaskOutput` with that ID to read\n  the task's output and details.\n- This tool is read-only and does not change any state, so it is always safe\n  to call, including in plan mode.\n";
+var task_list_default = "List background tasks and their current status.\n\nUse this tool to discover which background tasks exist and where each one\nstands. It is the entry point for inspecting background work: it returns a\ntask ID, status, command, description, and PID for every task it reports,\nplus the exit code and stop reason for tasks that have already finished.\n\nGuidelines:\n\n- After a context compaction, or whenever you are unsure which background\n  tasks are running or what their task IDs are, call this tool to\n  re-enumerate them instead of guessing a task ID.\n- Pass `active_only=false` only when you specifically need to see tasks that\n  have already finished. With `active_only=false` the result may also include\n  `lost` tasks — tasks left over from a previous process that can no longer be\n  inspected or controlled; treat them as already terminated.\n- This tool only lists tasks; it does not return their output. Use it first\n  to locate the task ID you need, then call `TaskOutput` with that ID to read\n  the task's output and details.\n- This tool is read-only and does not change any state, so it is always safe\n  to call, including in plan mode.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/background/task-list.ts
 /**
@@ -54739,7 +54751,7 @@ function oneShotJitteredNextCronRunMs(task, idealMs, config = DEFAULT_CRON_JITTE
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/cron/cron-create.md
-var cron_create_default = "Schedule a prompt to be enqueued at a future time. Use for both recurring schedules and one-shot reminders.\n\nUses standard 5-field cron in the user's local timezone: minute hour day-of-month month day-of-week. `0 9 * * *` means 9am local — no timezone conversion needed.\n\n## One-shot tasks (recurring: false)\n\nFor \"remind me at X\" or \"at <time>, do Y\" requests — fire once then auto-delete.\nPin minute/hour/day-of-month/month to specific values:\n  \"remind me at 2:30pm today to check the deploy\" → cron: \"30 14 <today_dom> <today_month> *\", recurring: false\n  \"tomorrow morning, run the smoke test\" → cron: \"57 8 <tomorrow_dom> <tomorrow_month> *\", recurring: false\n\n## Recurring jobs (recurring: true, the default)\n\nFor \"every N minutes\" / \"every hour\" / \"weekdays at 9am\" requests:\n  \"*/5 * * * *\" (every 5 min), \"0 * * * *\" (hourly), \"0 9 * * 1-5\" (weekdays at 9am local)\n\n## Avoid the :00 and :30 minute marks when the task allows it\n\nEvery user who asks for \"9am\" gets `0 9`, and every user who asks for \"hourly\" gets `0 *` — which means requests from across the planet land on the API at the same instant. When the user's request is approximate, pick a minute that is NOT 0 or 30:\n  \"every morning around 9\" → \"57 8 * * *\" or \"3 9 * * *\" (not \"0 9 * * *\")\n  \"hourly\" → \"7 * * * *\" (not \"0 * * * *\")\n  \"in an hour or so, remind me to...\" → pick whatever minute you land on, don't round\n\nOnly use minute 0 or 30 when the user names that exact time and clearly means it (\"at 9:00 sharp\", \"at half past\", coordinating with a meeting). When in doubt, nudge a few minutes early or late — the user will not notice, and the fleet will.\n\n## Coalesce semantics\n\nIf the scheduler slept past multiple ideal fire times (laptop closed, long-running turn, etc.), only **one** fire is delivered when it wakes up. The origin carries `coalescedCount` showing how many ideal fires were collapsed into this single delivery. You should treat `coalescedCount > 1` as \"I missed some checks; only the latest state matters\" rather than running the prompt that many times.\n\n## Cron-fire envelope\n\nWhen a cron task fires, the prompt you scheduled is re-injected wrapped in an XML envelope that exposes the fire context:\n\n```\n<cron-fire jobId=\"...\" cron=\"...\" recurring=\"true|false\" coalescedCount=\"N\" stale=\"true|false\">\n<prompt>\nyour original prompt text, verbatim\n</prompt>\n</cron-fire>\n```\n\nThe envelope is parseable. Use `coalescedCount > 1` to know multiple ideal fires were collapsed into a single delivery (treat as \"only the latest state matters\"), and `stale=\"true\"` as a cue that the task is past its 7-day threshold.\n\n## 7-day stale behavior\n\nRecurring tasks that have been alive for more than 7 days fire one\nfinal time with `stale: true` on the envelope, and the system then\nauto-deletes the task. The flag is the model's notice that this is\nthe last delivery. If the schedule is still wanted, call `CronCreate`\nagain with the same `cron` and `prompt` — that resets `createdAt` and\nstarts a fresh 7-day window. One-shot tasks are never marked stale.\n\nBench / acceptance runs can set `SCREAM_CRON_NO_STALE=1` to disable the\njudgment entirely.\n\n## Jitter behavior\n\nAnti-herd jitter is applied deterministically per task id:\n  - Recurring: ideal fire time is shifted **forward** by an offset ≤ min(10% of the cron period, 15 minutes). A `*/5 * * * *` task can drift up to 30s; a `0 9 * * *` task can drift up to 15 minutes.\n  - One-shot: only when the ideal fire lands on `:00` or `:30` of the hour, the fire is pulled **earlier** by ≤ 90 seconds. Other minutes pass through unchanged.\n\nBench / acceptance tests can set `SCREAM_CRON_NO_JITTER=1` to disable jitter entirely.\n\n## One-shot vs recurring — when to pick which\n\nUse `recurring: false` for \"remind me at X\" style requests, single deadlines, \"in N minutes do Y\", and any task that should not repeat. Use `recurring: true` for periodic polling (CI status, build watchers, scheduled reports), workday rituals, and anything the user explicitly described as recurring.\n\n## Session lifetime\n\nCron tasks live in the current scream CLI session. When you exit, they\nare persisted under the session homedir; the next `scream resume` of the\nsame session reloads them and the scheduler resumes from each task's\n`createdAt`. Fire times that fell during the offline window are\ncollapsed into a single delivery via `coalescedCount` (and recurring\ntasks past their 7-day window arrive with `stale: true` as their final\ndelivery).\n\nTasks do **not** carry over into a brand-new session — they are scoped\nto the resumed session id, not to the working directory.\n\n## Returned fields\n\n`id` (8-hex), `humanSchedule` (English summary), `recurring`,\n`nextFireAt` (ISO timestamp or null). `id` is needed by `CronDelete`.\n";
+var cron_create_default = "Schedule a prompt to be enqueued at a future time. Use for both recurring schedules and one-shot reminders.\n\n`0 9 * * *` means 9am local — no timezone conversion needed.\n\n## One-shot tasks (recurring: false)\n\nFor \"remind me at X\" or \"at <time>, do Y\" requests — fire once then auto-delete.\nPin minute/hour/day-of-month/month to specific values:\n  \"remind me at 2:30pm today to check the deploy\" → cron: \"30 14 <today_dom> <today_month> *\", recurring: false\n  \"tomorrow morning, run the smoke test\" → cron: \"57 8 <tomorrow_dom> <tomorrow_month> *\", recurring: false\n\n## Recurring jobs\n\nFor \"every N minutes\" / \"every hour\" / \"weekdays at 9am\" requests:\n  \"*/5 * * * *\" (every 5 min), \"0 * * * *\" (hourly), \"0 9 * * 1-5\" (weekdays at 9am local)\n\n## Avoid the :00 and :30 minute marks when the task allows it\n\nEvery user who asks for \"9am\" gets `0 9`, and every user who asks for \"hourly\" gets `0 *` — which means requests from across the planet land on the API at the same instant. When the user's request is approximate, pick a minute that is NOT 0 or 30:\n  \"every morning around 9\" → \"57 8 * * *\" or \"3 9 * * *\" (not \"0 9 * * *\")\n  \"hourly\" → \"7 * * * *\" (not \"0 * * * *\")\n  \"in an hour or so, remind me to...\" → pick whatever minute you land on, don't round\n\nOnly use minute 0 or 30 when the user names that exact time and clearly means it (\"at 9:00 sharp\", \"at half past\", coordinating with a meeting). When in doubt, nudge a few minutes early or late — the user will not notice, and the fleet will.\n\n## Coalesce semantics\n\nIf the scheduler slept past multiple ideal fire times (laptop closed, long-running turn, etc.), only **one** fire is delivered when it wakes up. The origin carries `coalescedCount` showing how many ideal fires were collapsed into this single delivery. You should treat `coalescedCount > 1` as \"I missed some checks; only the latest state matters\" rather than running the prompt that many times.\n\n## Cron-fire envelope\n\nWhen a cron task fires, the prompt you scheduled is re-injected wrapped in an XML envelope that exposes the fire context:\n\n```\n<cron-fire jobId=\"...\" cron=\"...\" recurring=\"true|false\" coalescedCount=\"N\" stale=\"true|false\">\n<prompt>\nyour original prompt text, verbatim\n</prompt>\n</cron-fire>\n```\n\nThe envelope is parseable. Use `coalescedCount > 1` to know multiple ideal fires were collapsed into a single delivery (treat as \"only the latest state matters\"), and `stale=\"true\"` as a cue that the task is past its 7-day threshold.\n\n## 7-day stale behavior\n\nRecurring tasks that have been alive for more than 7 days fire one\nfinal time with `stale: true` on the envelope, and the system then\nauto-deletes the task. The flag is the model's notice that this is\nthe last delivery. If the schedule is still wanted, call `CronCreate`\nagain with the same `cron` and `prompt` — that resets `createdAt` and\nstarts a fresh 7-day window. One-shot tasks are never marked stale.\n\nBench / acceptance runs can set `SCREAM_CRON_NO_STALE=1` to disable the\njudgment entirely.\n\n## Jitter behavior\n\nAnti-herd jitter is applied deterministically per task id:\n  - Recurring: ideal fire time is shifted **forward** by an offset ≤ min(10% of the cron period, 15 minutes). A `*/5 * * * *` task can drift up to 30s; a `0 9 * * *` task can drift up to 15 minutes.\n  - One-shot: only when the ideal fire lands on `:00` or `:30` of the hour, the fire is pulled **earlier** by ≤ 90 seconds. Other minutes pass through unchanged.\n\nBench / acceptance tests can set `SCREAM_CRON_NO_JITTER=1` to disable jitter entirely.\n\n## One-shot vs recurring — when to pick which\n\nUse one-shot for \"remind me at X\" style requests, single deadlines, and any task that should not repeat. Use recurring for periodic polling (CI status, build watchers, scheduled reports), workday rituals, and anything the user explicitly described as recurring.\n\n## Session lifetime\n\nCron tasks live in the current scream CLI session. When you exit, they\nare persisted under the session homedir; the next `scream resume` of the\nsame session reloads them and the scheduler resumes from each task's\n`createdAt`. Fire times that fell during the offline window are\ncollapsed into a single delivery via `coalescedCount` (and recurring\ntasks past their 7-day window arrive with `stale: true` as their final\ndelivery).\n\nTasks do **not** carry over into a brand-new session — they are scoped\nto the resumed session id, not to the working directory.\n\n## Returned fields\n\n`id` (8-hex), `humanSchedule` (English summary), `recurring`,\n`nextFireAt` (ISO timestamp or null). `id` is needed by `CronDelete`.\n";
 /**
 * Hard ceiling on `prompt` byte length (UTF-8). The zod `.max(...)`
 * upstream is in code units, which underflows multi-byte input
@@ -54860,7 +54872,7 @@ function formatOutput(o) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/cron/cron-delete.md
-var cron_delete_default = "Cancel a scheduled cron job by id.\n\nUse this tool to remove a cron task previously scheduled with\n`CronCreate`. The `id` is the 8-hex value returned by `CronCreate`, or\nshown in the `id:` column of `CronList` — quote it verbatim, no\nprefix.\n\nBehaviour by task kind:\n\n- **Recurring task** (`recurring: true`): stops all future fires\n  immediately. The scheduler picks up the deletion on its next tick.\n- **One-shot task** (`recurring: false`): cancels the pending fire if\n  it has not happened yet. One-shots that have already fired\n  auto-delete themselves, so calling `CronDelete` on a fired one-shot\n  returns \"no cron job with id ...\".\n\nNot-found is reported as an error (not a silent no-op) so you can\ncorrect yourself — typically by calling `CronList` to see which ids\nare actually live, rather than re-trying with the same stale id.\n\nRefresh pattern (use when you want a stale recurring schedule to\ncontinue):\n\nStale recurring tasks are auto-deleted by the system after their final\nfire — there is nothing for `CronDelete` to remove at that point. To\nkeep the schedule running, just call `CronCreate` with the same `cron`\nand `prompt`. Use `CronList`'s `prompt` field to recall the original\ntext after a context compaction.\n\n`CronDelete` remains the right call when you want to cancel a task\nthat is still live (recurring not yet stale, or a one-shot still\npending).\n\nGuidelines:\n\n- Cron deletion is irreversible — there is no undo. If you delete the\n  wrong task, you must re-create it with `CronCreate`.\n- If the model is unsure which id is current (e.g. after a context\n  compaction), call `CronList` first rather than guessing.\n";
+var cron_delete_default = "Cancel a scheduled cron job by id.\n\nUse this tool to remove a cron task previously scheduled with\n`CronCreate`. Quote the id verbatim, no prefix.\n\nBehaviour by task kind:\n\n- **Recurring task** (`recurring: true`): stops all future fires\n  immediately. The scheduler picks up the deletion on its next tick.\n- **One-shot task** (`recurring: false`): cancels the pending fire if\n  it has not happened yet. One-shots that have already fired\n  auto-delete themselves, so calling `CronDelete` on a fired one-shot\n  returns \"no cron job with id ...\".\n\nNot-found is reported as an error (not a silent no-op) so you can\ncorrect yourself — typically by calling `CronList` to see which ids\nare actually live, rather than re-trying with the same stale id.\n\nRefresh pattern (use when you want a stale recurring schedule to\ncontinue):\n\nStale recurring tasks are auto-deleted by the system after their final\nfire — there is nothing for `CronDelete` to remove at that point. To\nkeep the schedule running, just call `CronCreate` with the same `cron`\nand `prompt`. Use `CronList`'s `prompt` field to recall the original\ntext after a context compaction.\n\n`CronDelete` remains the right call when you want to cancel a task\nthat is still live (recurring not yet stale, or a one-shot still\npending).\n\nGuidelines:\n\n- Cron deletion is irreversible — there is no undo. If you delete the\n  wrong task, you must re-create it with `CronCreate`.\n- If the model is unsure which id is current (e.g. after a context\n  compaction), call `CronList` first rather than guessing.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/cron/cron-delete.ts
 /**
@@ -55471,7 +55483,7 @@ function filterSubagentsBySpawns$1(subagents, allowedSpawns) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/ask-user.md
-var ask_user_default = "Use this tool when you need to ask the user questions with structured options during execution. This allows you to:\n1. Collect user preferences or requirements before proceeding\n2. Resolve ambiguous or underspecified instructions\n3. Let the user decide between implementation approaches as you work\n4. Present concrete options when multiple valid directions exist\n\n**When NOT to use:**\n- When you can infer the answer from context — be decisive and proceed\n- Trivial decisions that don't materially affect the outcome\n\nOverusing this tool interrupts the user's flow. Only use it when the user's input genuinely changes your next action.\n\n**Usage notes:**\n- Users always have an \"Other\" option for custom input — don't create one yourself\n- Use multi_select to allow multiple answers to be selected for a question\n- Keep option labels concise (1-5 words), use descriptions for trade-offs and details\n- Each question should have 2-4 meaningful, distinct options\n- You can ask 1-4 questions at a time; group related questions to minimize interruptions\n- If you recommend a specific option, list it first and append \"(Recommended)\" to its label";
+var ask_user_default = "Use this tool when you need to ask the user questions with structured options during execution. This allows you to:\n1. Collect user preferences or requirements before proceeding\n2. Resolve ambiguous or underspecified instructions\n3. Let the user decide between implementation approaches as you work\n4. Present concrete options when multiple valid directions exist\n\n**When NOT to use:**\n- When you can infer the answer from context - be decisive and proceed\n- Trivial decisions that don't materially affect the outcome\n\nOverusing this tool interrupts the user's flow. Only use it when the user's input genuinely changes your next action.\n\n**Usage notes:**\n- Group related questions to minimize interruptions.\n- If you recommend a specific option, list it first.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/ask-user.ts
 /**
@@ -55719,7 +55731,7 @@ const SetGoalBudgetToolInputSchema = z.object({
 var SetGoalBudgetTool = class {
 	agent;
 	name = "SetGoalBudget";
-	description = "Set a hard budget limit for the current goal. Accepts one limit at a time (turns, tokens, or time). The goal will be blocked when the budget is reached.";
+	description = "Set a hard budget limit for the current goal. The goal will be blocked when the budget is reached.";
 	parameters = toInputJsonSchema(SetGoalBudgetToolInputSchema);
 	constructor(agent) {
 		this.agent = agent;
@@ -56223,6 +56235,85 @@ function formatTokens$2(tokens) {
 	return `${(tokens / 1e6).toFixed(1)}M`;
 }
 //#endregion
+//#region ../../packages/agent-core/src/tools/builtin/goal/emission-guard.ts
+/**
+* Grader emission guard - deduplicates and filters grader (referee) feedback
+* before it is injected into the agent context.
+*
+* Without this guard, a grader that repeatedly returns the same FAIL reason
+* (e.g. "redo", "not right") causes the identical feedback to be appended to
+* context on every submission. This wastes context budget and can trap the
+* agent in a loop where it keeps retrying without new information.
+*
+* Inspired by oh-my-pi's `advisor/emission-guard.ts`, but adapted for
+* scream-code's grader model: the grader is called once per `complete`
+* submission (not continuously), so per-round limiting is unnecessary. The
+* guard focuses on normalization, content-free filtering, and exact-text
+* deduplication keyed by goal objective.
+*/
+/** Short phrases that carry no actionable feedback. */
+const CONTENT_FREE_PHRASES = new Set([
+	"stop",
+	"done",
+	"lgtm",
+	"no issue",
+	"redo",
+	"try again",
+	"not good enough",
+	"fix it",
+	"wrong",
+	"incorrect",
+	"bad",
+	"重做",
+	"不对",
+	"不行",
+	"继续",
+	"再做",
+	"错误",
+	"不行",
+	"不好",
+	"改"
+]);
+/** Maximum number of historically seen feedback texts retained per goal. */
+const MAX_SEEN_PER_GOAL = 16;
+/** Phrases at or below this length are checked against the content-free set. */
+function isContentFree(text) {
+	const lower = text.toLowerCase().trim();
+	return CONTENT_FREE_PHRASES.has(lower);
+}
+/**
+* Filters grader feedback before injection into the agent context.
+*
+* Returns the denoised feedback text if it should be injected, or `null` if
+* the feedback is empty, content-free, or an exact duplicate of a previously
+* seen feedback for the same goal. The caller should skip injection when
+* `null` is returned.
+*
+* @param reason The raw grader FAIL reason.
+* @param goalKey A stable identifier for the current goal (e.g. the objective
+*   text). Different goals get independent deduplication buckets.
+*/
+var GraderEmissionGuard = class {
+	seenByGoal = /* @__PURE__ */ new Map();
+	filter(reason, goalKey) {
+		const normalized = reason.normalize("NFKC").trim();
+		if (normalized.length === 0) return null;
+		if (isContentFree(normalized)) return null;
+		const key = normalized.toLowerCase();
+		const bucket = this.seenByGoal.get(goalKey);
+		if (bucket !== void 0 && bucket.includes(key)) return null;
+		const next = bucket ?? [];
+		next.push(key);
+		if (next.length > MAX_SEEN_PER_GOAL) next.shift();
+		this.seenByGoal.set(goalKey, next);
+		return normalized;
+	}
+	/** Clear the deduplication bucket for a goal (e.g. on goal change). */
+	resetGoal(goalKey) {
+		this.seenByGoal.delete(goalKey);
+	}
+};
+//#endregion
 //#region ../../packages/agent-core/src/tools/builtin/goal/update-goal.ts
 const UpdateGoalToolInputSchema = z.object({
 	status: z.enum([
@@ -56236,6 +56327,11 @@ const UpdateGoalToolInputSchema = z.object({
 const MAX_GRADER_OUTPUT_CHARS = 4e3;
 /** Maximum characters of `git diff --stat HEAD` to append to the grader input. */
 const MAX_DIFF_STAT_CHARS = 2e3;
+/**
+* Module-level emission guard. Deduplicates grader FAIL feedback per goal so
+* the referee cannot trap the agent in a loop by repeating the same reason.
+*/
+const graderEmissionGuard = new GraderEmissionGuard();
 function extractRecentOutput(history) {
 	const parts = [];
 	for (let i = history.length - 1; i >= 0; i--) {
@@ -56372,6 +56468,7 @@ var UpdateGoalTool = class {
 		if (grade.pass) {
 			try {
 				const completed = await goal.markComplete({}, "model");
+				graderEmissionGuard.resetGoal(goalState.objective);
 				if (completed === null) return toolError("Failed to mark verified goal complete", goal);
 				this.agent.context.appendSystemReminder(buildGoalCompletionSummaryPrompt(completed), {
 					kind: "system_trigger",
@@ -56385,8 +56482,12 @@ var UpdateGoalTool = class {
 				stopTurn: true
 			};
 		}
-		this.appendGradingFeedback(grade.reason);
-		return { output: `Verification failed: ${grade.reason}. Continue working.` };
+		const denoised = graderEmissionGuard.filter(grade.reason, goalState.objective);
+		if (denoised !== null) {
+			this.appendGradingFeedback(denoised);
+			return { output: `Verification failed: ${denoised}. Continue working.` };
+		}
+		return { output: "Previous verification feedback still applies. Address the earlier feedback and retry." };
 	}
 	appendGradingFeedback(reason) {
 		this.agent.context.appendSystemReminder(buildGradingFeedbackPrompt(reason), {
@@ -56427,7 +56528,7 @@ const WriteGoalNoteInputSchema = z.object({ content: z.string().min(1).max(400).
 var WriteGoalNoteTool = class {
 	agent;
 	name = "WriteGoalNote";
-	description = "Record a working note during goal execution. Notes persist across continuation turns and are injected automatically. Use this to record facts you verified, dead ends you hit, decisions you made, or anything future-you should not re-derive.";
+	description = "Record a working note during goal execution. Use this for dead ends you hit, decisions you made, or anything future-you should not re-derive.";
 	parameters = toInputJsonSchema(WriteGoalNoteInputSchema);
 	constructor(agent) {
 		this.agent = agent;
@@ -58303,7 +58404,7 @@ const MemoryLookupInputSchema = z.object({
 var MemoryLookupTool = class {
 	agent;
 	name = "MemoryLookup";
-	description = "Search the memory memo store for historical experiences from past user tasks. Call this when the current task may benefit from prior work, when you encounter a repeating error or pattern, or when you are unsure of the best approach. Returns memos ranked by relevance, including the approach taken, the outcome, what failed, what worked, project, and tags. By default searches globally; use scope: project to restrict results to the current project.";
+	description = "Search the memory memo store for historical experiences from past user tasks. Call this when the current task may benefit from prior work, when you encounter a repeating error or pattern, or when you are unsure of the best approach. Returns memos ranked by relevance, including the approach taken, the outcome, what failed, what worked, project, and tags.";
 	parameters = toInputJsonSchema(MemoryLookupInputSchema);
 	constructor(agent) {
 		this.agent = agent;
@@ -58405,7 +58506,7 @@ const MemoryWriteInputSchema = z.object({
 var MemoryWriteTool = class {
 	agent;
 	name = "MemoryWrite";
-	description = "Write a new memory memo to the global memory memo store. Call this when the user explicitly asks to save an experience, lesson, or summary to memory, for example \"保存到记忆\", \"保存到备忘录\", \"总结并保存\", \"永久记忆\", \"记录我的记忆\", \"记住这个\", \"添加到记忆\", or \"存入记忆库\". Summarize the user need, approach taken, final outcome, what failed, what worked, and 3-5 tags.";
+	description = "Write a new memory memo to the global memory memo store. Call this when the user explicitly asks to save an experience, lesson, or summary to memory, for example \"保存到记忆\", \"保存到备忘录\", \"总结并保存\", \"永久记忆\", \"记录我的记忆\", \"记住这个\", \"添加到记忆\", or \"存入记忆库\".";
 	parameters = toInputJsonSchema(MemoryWriteInputSchema);
 	constructor(agent) {
 		this.agent = agent;
@@ -58971,8 +59072,7 @@ var LspTool = class {
 	lspRegistry;
 	name = "LSP";
 	description = [
-		"Query a language server for code intelligence.",
-		"Use 'references' to find all usages of a symbol, 'definition' to jump to where a symbol is defined, 'diagnostics' to get type errors and warnings for a file, and 'rename' to rename a symbol across all its references.",
+		"Query a language server for code intelligence: find usages, jump to definitions, get diagnostics, or rename a symbol across all references.",
 		"The language server is started automatically for supported file types (TypeScript/JavaScript, Python, Rust, Go).",
 		"Rename requires the typescript-language-server (or equivalent) binary on PATH for the file type."
 	].join(" ");
@@ -62802,20 +62902,20 @@ function isRecord$6(value) {
 var dream_default = "---\nname: dream\ndescription: 整理记忆库 — 合并重复、解决矛盾、清理过时条目\n---\n\n# Dream: 记忆合并整理\n\n用户调用了 `/dream`。你要对全局记忆库进行一次完整的整理和清理。\n\n记忆库是**全局**的，所有会话的记忆都保存在同一个 SQLite 数据库里（`<screamHomeDir>/memory/memos.sqlite`），不是按会话分散存放。\n\n## 前置检查\n\n1. 调用 `MemoryConsolidatePlan` 工具获取整理计划。\n   - 如果返回\"记忆库为空\"，告知用户\"记忆库为空，无需整理\"并停止。\n   - 否则你会得到一个 JSON 计划，包含：duplicateGroups（重复组）、resolved（已完成条目）、stale（过时条目）、summary（统计）。\n\n2. 不要直接修改记忆文件。所有删除和写入都通过 `MemoryConsolidateApply` 工具完成。\n\n## 整理计划展示\n\n把计划转换成用户可读的格式：\n\n```\n## Dream 整理计划\n\n### 概况\n- 当前共 X 条记忆\n- 重复组：N 组\n- 建议删除：M 条（已完成 + 过时）\n- 整理后预计：Y 条\n\n### 重复合并（N 组）\n**组 1: 修复登录 token 刷新**\n- memo-abc123 (2026-05-01, 完成) — \"登录页 token 过期需要手动刷新\"\n- memo-def456 (2026-05-10, 完成) — \"登录 token 过期问题修复\"\n→ 合并为: \"修复登录页 token 过期问题。方案: 在 axios 拦截器中添加自动 refresh 逻辑...\"\n  结果: 完成\n\n### 建议删除（M 条）\n- memo-xyz789: \"添加暗色模式\" (完成, 2026-04-01) — 已完成超过 2 个月\n- memo-old001: \"尝试某方案\" (放弃, 2026-03-01) — 过时\n\n### 总结\n- 合并: N 组 → 减少 X 条\n- 删除: M 条\n- 整理后: 共 Y 条记忆\n```\n\n用 AskUserQuestion 让用户选择：\n- \"执行整理\" — 按上述计划执行\n- \"仅显示计划\" — 不做修改，直接结束\n- \"取消\"\n\n## 执行整理\n\n如果用户选择\"执行整理\"：\n\n1. 直接把 `MemoryConsolidatePlan` 返回的完整 JSON 计划作为参数，调用 `MemoryConsolidateApply`。\n2. 工具会自动完成以下操作：\n   - 删除重复组中的原记忆\n   - 为每组重复记忆追加一条合并后的新记忆（字段格式由工具保证正确）\n   - 删除已完成和过时的记忆\n   - 更新 `dream-lock.json`，重置建议计数器\n3. 向用户报告工具返回的结果：\"已删除 X 条，创建 Y 条合并记忆。记忆库整理完成。\"\n\n## 重要规则\n\n- **仅合并高度重复的记忆**。只有当两条记忆描述的是同一件事、同一个问题、同一个修复方案时才可合并。如果只是主题相关但细节不同（如两个不同的 bug、两个不同的优化方向），**绝对不能合并**。宁可多保留十条，不可误删一条。\n- 如果 `MemoryConsolidatePlan` 标记的某组重复实际上并不是同一件事，在展示计划时把它从\"重复合并\"里去掉，只保留你确信重复的组，再把精简后的计划传给 `MemoryConsolidateApply`。\n- 不确定时保留原文，不要猜测删除。\n- 操作前必须得到用户确认，不能擅自执行。\n- 不要手动写 Bash 去修改 `entries.jsonl`，统一通过 `MemoryConsolidateApply` 工具执行。\n";
 //#endregion
 //#region ../../packages/agent-core/src/skill/builtin/dream.ts
-const PSEUDO_PATH$2 = "builtin://dream";
-const parsed$2 = parseSkillText({
+const PSEUDO_PATH$1 = "builtin://dream";
+const parsed$1 = parseSkillText({
 	skillMdPath: "/builtin/skills/dream.md",
 	skillDirName: "dream",
 	source: "builtin",
 	text: dream_default
 });
 const DREAM_SKILL = {
-	...parsed$2,
-	path: PSEUDO_PATH$2,
-	dir: PSEUDO_PATH$2,
+	...parsed$1,
+	path: PSEUDO_PATH$1,
+	dir: PSEUDO_PATH$1,
 	metadata: {
-		...parsed$2.metadata,
-		type: parsed$2.metadata.type ?? "inline",
+		...parsed$1.metadata,
+		type: parsed$1.metadata.type ?? "inline",
 		disableModelInvocation: true
 	}
 };
@@ -62824,36 +62924,14 @@ const DREAM_SKILL = {
 var make_skill_default = "---\nname: make-skill\ndescription: 从当前会话上下文沉淀工作流为可复用 Skill\n---\n\n# Make Skill: 从上下文提炼 Skill\n\n用户调用了 `/make-skill`。你的任务是通过对话引导用户，把当前会话中解决问题的方式沉淀为一个可复用的 Scream Code Skill，并安装到插件中心。\n\n## 激活参数\n\n本次激活的参数：\n\n```json\n$ARGUMENTS\n```\n\n- `initialRequest`：用户输入 `/make-skill` 时附带的一句话描述，可能为空。\n\n## 工作方式\n\n这不是一次性任务。你需要通过**多轮对话**澄清以下信息，每一轮只问一个问题，等用户回答后再进入下一阶段：\n\n1. Skill 类型（`workflow` / `code-pattern` / `troubleshooting` / `tool-chain` / `custom`）\n2. Skill 名称（kebab-case）\n3. 这个 Skill 主要解决什么问题\n4. 希望重点关注哪些内容\n5. 生成草案并确认安装\n\n## 阶段判断\n\n根据当前对话历史判断你处于哪个阶段：\n\n- **阶段 0**：本 Skill 刚激活，还没有问过任何问题。先分析会话上下文和 `initialRequest`，然后用 `AskUserQuestion` 询问 Skill 类型。\n- **阶段 1**：已经确定了 Skill 类型，但还没有确定名称。根据类型和上下文建议一个 kebab-case 名称，用 `AskUserQuestion` 询问用户是否接受或修改。\n- **阶段 2**：已经确定了名称，但还没有明确解决的问题。根据上下文总结一句话描述，用 `AskUserQuestion` 询问用户是否接受或修改。\n- **阶段 3**：已经确定了问题，但还没有明确关注重点。给出 2-4 个关注重点建议，用 `AskUserQuestion` 让用户选择或输入。\n- **阶段 4**：类型、名称、问题、重点都已确定。调用 `MakeSkillPlanTool` 生成草案，展示给用户，并用 `AskUserQuestion` 询问是否确认安装。\n- **阶段 5**：用户已确认安装。调用 `MakeSkillApplyTool` 写入插件中心。\n\n如何判断“已确定”：历史消息中已经有你提出的 `AskUserQuestion` 以及用户给出的明确回答（或选择了你建议的选项）。\n\n## 每轮提问规范\n\n除非处于阶段 4/5，否则**每轮必须也只允许使用一次 `AskUserQuestion`**。不要直接用普通文本提问，这样无法给用户结构化选项。\n\n### 阶段 0：询问 Skill 类型\n\n先分析当前会话上下文，判断最可能想沉淀什么。给出 2-4 个建议选项，不要列出全部 5 种。把最相关的放在最前面，并标记 `(Recommended)`。\n\n示例问题：\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"根据刚才的会话，你想把什么沉淀成 Skill？\",\n      \"header\": \"类型\",\n      \"options\": [\n        { \"label\": \"Code pattern (Recommended)\", \"description\": \"把 React 表单验证的代码模式提炼为可复用模板\" },\n        { \"label\": \"Workflow\", \"description\": \"把解决表单验证问题的步骤沉淀为流程\" },\n        { \"label\": \"Troubleshooting\", \"description\": \"把常见验证错误排查过程沉淀为诊断指南\" }\n      ],\n      \"multi_select\": false\n    }\n  ]\n}\n```\n\n注意：系统会自动添加 \"Other\" 选项，**不要自己添加**。如果用户想选未列出的类型（如 `tool-chain` 或 `custom`），他们会通过 Other 输入。\n\n### 阶段 1：询问 Skill 名称\n\n根据已确定的类型和上下文，建议一个 kebab-case 名称。用 `AskUserQuestion` 让用户接受、修改或自己输入。\n\n示例：\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"建议把这个 Skill 命名为 react-form-validate，是否接受？\",\n      \"header\": \"名称\",\n      \"options\": [\n        { \"label\": \"使用 react-form-validate (Recommended)\", \"description\": \"简洁直观，符合 kebab-case\" },\n        { \"label\": \"换一个名称\", \"description\": \"我给出其他建议\" },\n        { \"label\": \"我自己输入\", \"description\": \"手动指定名称\" }\n      ],\n      \"multi_select\": false\n    }\n  ]\n}\n```\n\n如果用户选择“换一个名称”或“我自己输入”，你需要在下一轮继续用 `AskUserQuestion` 给出新建议或请求输入。\n\n### 阶段 2：询问解决的问题\n\n根据上下文总结一句话描述，让用户接受、修改或自己输入。\n\n示例：\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"这个 Skill 主要用于：在 React 中用 zod + react-hook-form 实现表单验证。是否准确？\",\n      \"header\": \"用途\",\n      \"options\": [\n        { \"label\": \"准确 (Recommended)\", \"description\": \"保持这个描述\" },\n        { \"label\": \"不够准确\", \"description\": \"我帮你调整\" },\n        { \"label\": \"我自己描述\", \"description\": \"手动输入用途\" }\n      ],\n      \"multi_select\": false\n    }\n  ]\n}\n```\n\n### 阶段 3：询问关注重点\n\n给出 2-4 个基于上下文的关注重点建议。\n\n示例：\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"生成时希望重点关注哪些方面？\",\n      \"header\": \"重点\",\n      \"options\": [\n        { \"label\": \"验证 schema 定义 (Recommended)\", \"description\": \"重点提取 zod schema 的编写模式\" },\n        { \"label\": \"错误处理与提示\", \"description\": \"重点提取错误展示和反馈逻辑\" },\n        { \"label\": \"组件绑定方式\", \"description\": \"重点提取 react-hook-form 的绑定代码\" }\n      ],\n      \"multi_select\": true\n    }\n  ]\n}\n```\n\n### 阶段 4：展示草案并确认\n\n调用 `MakeSkillPlanTool`，参数：\n\n- `type`：阶段 0 确定的类型\n- `nameHint`：阶段 1 确定的名称\n- `purpose`：阶段 2 确定的问题描述\n- `focus`：阶段 3 确定的关注重点（多选用逗号连接成字符串）\n\n工具返回 JSON 后，用中文清晰展示：\n\n- Skill 名称和描述\n- 文件清单（至少包含 `SKILL.md`）\n- 适用场景\n- 安装位置：`~/.scream-code/plugins/managed/<name>/`，可通过 `/plugin` 管理\n\n然后用 `AskUserQuestion` 询问：\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"是否安装这个 Skill？\",\n      \"header\": \"确认\",\n      \"options\": [\n        { \"label\": \"确认安装 (Recommended)\", \"description\": \"写入插件中心并在新会话中可用\" },\n        { \"label\": \"取消\", \"description\": \"不保存任何内容\" }\n      ],\n      \"multi_select\": false\n    }\n  ]\n}\n```\n\n### 阶段 5：执行安装\n\n如果用户选择“确认安装”，调用 `MakeSkillApplyTool`，传入工具返回的完整草案 JSON（`name`、`description`、`content`、`files`）。\n\n把结果告知用户，例如：\n\n- 成功：`Skill 已安装到 ~/.scream-code/plugins/managed/<name>/。新会话中可通过 /<name> 调用。`\n- 失败：说明错误原因，不要重试。\n\n## 重要规则\n\n- 除了阶段 4 的展示文本外，**所有澄清问题都必须通过 `AskUserQuestion` 工具提出**，不要直接用文本回复提问。\n- 每轮只能问一个问题。等用户回答后再推进到下一阶段。\n- 不要在没有调用 `MakeSkillApplyTool` 的情况下直接写文件。\n- 如果用户选择“取消”或关闭问题，礼貌地告知已取消，不做任何修改。\n- 如果 `MakeSkillApplyTool` 返回错误（例如同名 Skill 已存在），向用户说明错误并停止，不要重试。\n- 新安装的 Skill 只在**新会话**中可用；当前会话不会立即加载它。\n- 安装后的 Skill 会出现在 `/plugin` 插件中心里，用户可以统一启用、禁用或卸载。\n";
 //#endregion
 //#region ../../packages/agent-core/src/skill/builtin/make-skill.ts
-const PSEUDO_PATH$1 = "builtin://make-skill";
-const parsed$1 = parseSkillText({
+const PSEUDO_PATH = "builtin://make-skill";
+const parsed = parseSkillText({
 	skillMdPath: "/builtin/skills/make-skill.md",
 	skillDirName: "make-skill",
 	source: "builtin",
 	text: make_skill_default
 });
 const MAKE_SKILL_SKILL = {
-	...parsed$1,
-	path: PSEUDO_PATH$1,
-	dir: PSEUDO_PATH$1,
-	metadata: {
-		...parsed$1.metadata,
-		type: parsed$1.metadata.type ?? "inline",
-		disableModelInvocation: true
-	}
-};
-//#endregion
-//#region ../../packages/agent-core/src/skill/builtin/tool-prompt-optimization/SKILL.md
-var SKILL_default = "---\nname: tool-prompt-optimization\ndescription: Audit and trim tool prompt text that duplicates information already inferable from the tool's JSON schema, reducing system prompt token cost.\n---\n\n# Tool Prompt Optimization\n\nA meta-skill for cutting system-prompt token waste: tool `description` text often\nrestates field names, types, and constraints that the Zod/JSON schema already\nencodes. Use a probe to measure the overlap, then trim what the model can infer\nfrom the schema alone.\n\n## When to use\n\n- System prompt token cost is high and tool descriptions are a meaningful share.\n- A tool's `description` repeats field names or types already in its schema.\n- Auditing tool definitions for redundancy before a release.\n\n## How to audit\n\n1. For each tool, lay the `description` text next to the Zod/JSON schema fields.\n2. Flag sentences that merely restate field names, types, or constraints already\n   encoded in the schema (e.g. \"command is a string\" when the schema already\n   declares `z.string()`).\n3. **Probe**: ask the model \"Given only the schema (no description), which\n   behaviors and constraints can you infer?\" The intersection is pure redundancy.\n4. Trim description text the model already infers from the schema alone.\n5. **Keep** what the schema cannot express:\n   - edge cases, gotchas, and ordering requirements\n   - cross-tool interactions and precedence rules\n   - safety-critical warnings and permission notes\n   - examples that disambiguate ambiguous schema fields\n\n## Rules\n\n- Never remove safety-critical warnings or permission notes.\n- Never remove examples that clarify ambiguous schema fields.\n- Before deleting a sentence, run `git blame` to check whether it was added to\n  fix a specific bug; if so, keep it (or confirm the bug is gone).\n- Measure the before/after token count to confirm savings actually materialized.\n- Prefer precise constraints over vague prose; if a constraint is enforceable in\n  the schema (e.g. `.min(1)`), move it there instead of describing it in text.\n";
-//#endregion
-//#region ../../packages/agent-core/src/skill/builtin/tool-prompt-optimization.ts
-const PSEUDO_PATH = "builtin://tool-prompt-optimization";
-const parsed = parseSkillText({
-	skillMdPath: "/builtin/skills/tool-prompt-optimization/SKILL.md",
-	skillDirName: "tool-prompt-optimization",
-	source: "builtin",
-	text: SKILL_default
-});
-const TOOL_PROMPT_OPTIMIZATION_SKILL = {
 	...parsed,
 	path: PSEUDO_PATH,
 	dir: PSEUDO_PATH,
@@ -62868,7 +62946,6 @@ const TOOL_PROMPT_OPTIMIZATION_SKILL = {
 function registerBuiltinSkills(registry) {
 	registry.registerBuiltinSkill(DREAM_SKILL);
 	registry.registerBuiltinSkill(MAKE_SKILL_SKILL);
-	registry.registerBuiltinSkill(TOOL_PROMPT_OPTIMIZATION_SKILL);
 }
 //#endregion
 //#region ../../packages/agent-core/src/skill/scanner.ts
@@ -71274,7 +71351,7 @@ function validateSkillPlan(plan, nameHint) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/wolfpack.md
-var wolfpack_default = "Use WolfPack to spawn multiple subagents in parallel for batch operations.\nThis is ideal when processing many independent items (files, checks, searches)\nthat all use the same subagent type and follow a similar pattern.\n\nInput:\n- description: Brief (3-5 word) task summary.\n- subagent_type: Subagent profile name. Defaults to \"coder\". Choose the profile\n  that best matches the batch task — using the right type materially improves\n  output quality. See the agent type list below for which type fits which job.\n- prompt_template: A prompt pattern where each item value is substituted in\n  to produce a per-item prompt. See the parameter schema for placeholder syntax.\n- items: Array of item strings. Each item gets its own subagent (no limit).\n\nItems must be independent — no subagent depends on another's output.\nIf items depend on each other, use separate Agent calls instead.\n\nChoosing subagent_type for the batch:\n- Batch code review, audit, or bug-finding across files → reviewer\n- Batch writing, reports, or long-form content → writer\n- Batch read-only exploration (find files, grep, understand modules) → explore\n- Batch verification (run build/test/lint per item) → verify\n- Batch deep debugging or architecture decisions → oracle\n- Batch planning or design work → plan\n- General engineering tasks with no specialised match → coder (default)\n\nExample: review source files for OWASP vulnerabilities by setting items to the file\npaths, subagent_type to \"reviewer\", and prompt_template to the review instruction.\nAll items are processed in parallel.\n\n";
+var wolfpack_default = "Use WolfPack to spawn multiple subagents in parallel for batch operations.\nThis is ideal when processing many independent items (files, checks, searches)\nthat all use the same subagent type and follow a similar pattern.\n\nItems must be independent - no subagent depends on another's output.\nIf items depend on each other, use separate Agent calls instead.\n\nChoosing subagent_type for the batch:\n- Batch code review, audit, or bug-finding across files -> reviewer\n- Batch writing, reports, or long-form content -> writer\n- Batch read-only exploration (find files, grep, understand modules) -> explore\n- Batch verification (run build/test/lint per item) -> verify\n- Batch deep debugging or architecture decisions -> oracle\n- Batch planning or design work -> plan\n- General engineering tasks with no specialised match -> coder (default)\n\nExample: review source files for OWASP vulnerabilities by setting items to the file\npaths, subagent_type to \"reviewer\", and prompt_template to the review instruction.\nAll items are processed in parallel.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/wolfpack.ts
 /**
@@ -71472,6 +71549,68 @@ function withTimeout$1(promise, timeoutMs, parentSignal) {
 	});
 }
 //#endregion
+//#region ../../packages/agent-core/src/tools/support/scan-cache.ts
+var FsScanCache = class {
+	cache = /* @__PURE__ */ new Map();
+	ttlMs;
+	maxEntries;
+	constructor({ ttlMs = 1e3, maxEntries = 16 } = {}) {
+		this.ttlMs = ttlMs;
+		this.maxEntries = maxEntries;
+	}
+	key(root, pattern, includeDirs) {
+		return `${root}\0${pattern}\0${String(includeDirs)}`;
+	}
+	/**
+	* Returns the cached output if present and not expired. Expired entries are
+	* deleted on access.
+	*/
+	get(root, pattern, includeDirs) {
+		const k = this.key(root, pattern, includeDirs);
+		const entry = this.cache.get(k);
+		if (entry === void 0) return void 0;
+		if (Date.now() - entry.createdAt > this.ttlMs) {
+			this.cache.delete(k);
+			return;
+		}
+		return entry.output;
+	}
+	/** Cache a scan output. Evicts the oldest entry when at capacity. */
+	set(root, pattern, includeDirs, output) {
+		if (this.cache.size >= this.maxEntries) {
+			let oldestKey;
+			let oldestTime = Infinity;
+			for (const [k, v] of this.cache) if (v.createdAt < oldestTime) {
+				oldestTime = v.createdAt;
+				oldestKey = k;
+			}
+			if (oldestKey !== void 0) this.cache.delete(oldestKey);
+		}
+		this.cache.set(this.key(root, pattern, includeDirs), {
+			output,
+			createdAt: Date.now()
+		});
+	}
+	/** Invalidate all cached entries rooted under the given directory path. */
+	invalidateByRoot(root) {
+		const prefix = `${root}\0`;
+		for (const k of this.cache.keys()) if (k.startsWith(prefix)) this.cache.delete(k);
+	}
+	/** Clear the entire cache (useful for tests). */
+	clear() {
+		this.cache.clear();
+	}
+	/** Number of cached entries (for tests / introspection). */
+	size() {
+		return this.cache.size;
+	}
+};
+/**
+* Module-level singleton shared by Glob (producer) and Edit/Write (invalidator).
+* Importing this instance ensures all tools reference the same cache.
+*/
+const scanCache = new FsScanCache();
+//#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/conflict-detect.ts
 /**
 * Detect unresolved git merge conflict markers in read output.
@@ -71718,7 +71857,7 @@ function hashEditPayload(input) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/edit.md
-var edit_default = "Perform exact string replacements against the text view returned by Read.\n\n- When copying from Read output, omit the line-number prefix and tab; match only the file content.\n- By default, old_string must occur exactly once. If it matches multiple locations, add surrounding context or set replace_all when every occurrence should change.\n- Prefer Edit for targeted changes to existing files; use Write only for new files or complete overwrites.\n- To modify a file, always use Edit; do not run a Shell `sed` command for edits.\n- When making several independent changes, issue multiple Edit calls in parallel within a single response; edits to the same file are serialized automatically by a write lock.\n- When several parallel Edit calls target the same file, a write lock serializes them; they apply in the order the calls appear in your response. An edit fails with `old_string not found` if its old_string was taken from text an earlier edit already replaced — base every old_string on the latest Read view and order dependent edits accordingly.\n- For pure CRLF files, Read shows LF and Edit.old_string/new_string should use LF; Edit writes the file back with CRLF preserved.\n- For mixed line endings or lone carriage returns, Read displays carriage returns as \\r; include actual \\r escapes in old_string/new_string for those positions.\n- When Read returned an `Anchor:` value in its status block, pass it as `anchor` to verify the file has not changed since it was read. If the anchor does not match, re-read the file before editing.\n- Edit refuses if `old_string` lands inside an unresolved merge conflict block, or if `new_string` would introduce `<<<<<<<`/`=======`/`>>>>>>>` markers. To clean up a conflict, include the markers in `old_string` so Edit replaces them.";
+var edit_default = "Perform exact string replacements against the text view returned by Read.\n\n- By default, old_string must occur exactly once. If it matches multiple locations, add surrounding context.\n- Prefer Edit for targeted changes to existing files; use Write only for new files or complete overwrites.\n- To modify a file, always use Edit; do not run a Shell `sed` command for edits.\n- When making several independent changes, issue multiple Edit calls in parallel within a single response; edits to the same file are serialized automatically by a write lock.\n- When several parallel Edit calls target the same file, a write lock serializes them; they apply in the order the calls appear in your response. An edit fails with `old_string not found` if its old_string was taken from text an earlier edit already replaced - base every old_string on the latest Read view and order dependent edits accordingly.\n- Edit refuses if `old_string` lands inside an unresolved merge conflict block, or if `new_string` would introduce `<<<<<<<`/`=======`/`>>>>>>>` markers. To clean up a conflict, include the markers in `old_string` so Edit replaces them.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/edit.ts
 const EditInputSchema = z.object({
@@ -71767,10 +71906,11 @@ var EditTool = class {
 				pathClass: this.jian.pathClass(),
 				homeDir: this.jian.gethome()
 			}),
-			execute: () => this.execution(args, path)
+			execute: ({ signal }) => this.execution(args, path, signal)
 		};
 	}
-	async execution(args, safePath) {
+	async execution(args, safePath, signal) {
+		signal?.throwIfAborted();
 		const result = await this.executionCore(args, safePath);
 		const inputHash = hashEditPayload({
 			path: args.path,
@@ -71867,6 +72007,7 @@ var EditTool = class {
 				}
 				const newContent = replaceOnceLiteral(content, args.old_string, args.new_string);
 				await this.jian.writeText(safePath, materializeModelText(newContent, modelView.lineEndingStyle));
+				scanCache.clear();
 				const { notice, hasErrors } = await this.appendDiagnostics(safePath);
 				const output = `Replaced 1 occurrence in ${args.path}${notice}`;
 				return hasErrors ? {
@@ -71885,6 +72026,7 @@ var EditTool = class {
 			}
 			const newContent = parts.join(args.new_string);
 			await this.jian.writeText(safePath, materializeModelText(newContent, modelView.lineEndingStyle));
+			scanCache.clear();
 			const { notice, hasErrors } = await this.appendDiagnostics(safePath);
 			const output = `Replaced ${String(replacementCount)} occurrences in ${args.path}${notice}`;
 			return hasErrors ? {
@@ -71981,7 +72123,7 @@ async function listDirectory(jian, workDir = jian.getcwd()) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/glob.md
-var glob_default = "Find files (and optionally directories) by glob pattern, sorted by modification time (most recent first).\n\nGood patterns:\n- `*.ts` — files in the current directory matching an extension\n- `src/**/*.ts` — recursive with a subdirectory anchor and extension\n- `test_*.py` — files whose name starts with a literal prefix\n\nRejected patterns (no literal anchor — nothing bounds the result set):\n- `**`, `**/*`, `*/*` — pure wildcards. Add an extension or subdirectory to give the walk a concrete target.\n- Anything that starts with `**/` (e.g. `**/*.md`, `**/main/*.py`). The leading `**/` has no literal anchor in front of it. Anchor it with a top-level subdirectory like `src/**/*.md`.\n- `*.{ts,tsx}` — brace expansion is not supported. Issue two calls: `*.ts` and `*.tsx`.\n\nLarge-directory warning — avoid recursing into dependency/build output even with an anchor:\n- `node_modules/**/*.js`, `.venv/**/*.py`, `__pycache__/**`, `target/**` all match technically but\n  typically produce thousands of results that truncate at the match cap and waste the caller context.\n  Prefer specific subpaths like `node_modules/react/src/**/*.js`.";
+var glob_default = "Find files (and optionally directories) by glob pattern, sorted by modification time (most recent first).\n\nGood patterns:\n- `*.ts` — files in the current directory matching an extension\n- `src/**/*.ts` — recursive with a subdirectory anchor and extension\n- `test_*.py` — files whose name starts with a literal prefix\n\nRejected patterns (no literal anchor — nothing bounds the result set):\n- `**`, `**/*`, `*/*` — pure wildcards. Add an extension or subdirectory to give the walk a concrete target.\n- Anything that starts with `**/` (e.g. `**/*.md`, `**/main/*.py`). The leading `**/` has no literal anchor in front of it. Anchor it with a top-level subdirectory like `src/**/*.md`.\n- `*.{ts,tsx}` — brace expansion is not supported. Issue two calls: `*.ts` and `*.tsx`.\n\nLarge-directory warning — avoid recursing into dependency/build output even with an anchor:\n- `node_modules/**/*.js`, `.venv/**/*.py`, `__pycache__/**`, `target/**` all match technically but\n  typically produce thousands of results that truncate at the {{ MAX_MATCHES }}-match cap and waste the caller context.\n  Prefer specific subpaths like `node_modules/react/src/**/*.js`.";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/glob.ts
 const GlobInputSchema = z.object({
@@ -71990,6 +72132,7 @@ const GlobInputSchema = z.object({
 	include_dirs: z.boolean().default(true).optional().describe("Whether to include directories in results. Defaults to true. Set false to return only files.")
 });
 const MAX_MATCHES = 1e3;
+const GLOB_DESCRIPTION = renderPrompt(glob_default, { MAX_MATCHES });
 /**
 * Path-shape hint appended to the tool description only on a Windows
 * (`win32` path class) backend. The `path` argument accepts both native
@@ -72019,7 +72162,7 @@ var GlobTool = class {
 	constructor(jian, workspace) {
 		this.jian = jian;
 		this.workspace = workspace;
-		this.description = this.jian.pathClass() === "win32" ? glob_default + WINDOWS_PATH_HINT : glob_default;
+		this.description = this.jian.pathClass() === "win32" ? GLOB_DESCRIPTION + WINDOWS_PATH_HINT : GLOB_DESCRIPTION;
 	}
 	async resolveExecution(args) {
 		let path;
@@ -72043,10 +72186,11 @@ var GlobTool = class {
 			},
 			approvalRule: literalRulePattern(this.name, args.pattern),
 			matchesRule: (ruleArgs) => matchesGlobRuleSubject(ruleArgs, args.pattern),
-			execute: () => this.execution(args, searchRoots)
+			execute: ({ signal }) => this.execution(args, searchRoots, signal)
 		};
 	}
-	async execution(args, searchRoots) {
+	async execution(args, searchRoots, signal) {
+		signal?.throwIfAborted();
 		if (startsWithDoubleStarPrefix(args.pattern)) {
 			let tree;
 			try {
@@ -72095,6 +72239,8 @@ var GlobTool = class {
 			}
 		}
 		try {
+			const cachedOutput = scanCache.get(searchRoots[0], args.pattern, includeDirs);
+			if (cachedOutput !== void 0) return { output: cachedOutput };
 			const seen = /* @__PURE__ */ new Set();
 			const entries = [];
 			const YIELD_SAFETY_CAP = MAX_MATCHES * 2;
@@ -72102,6 +72248,7 @@ var GlobTool = class {
 			let truncated = false;
 			outer: for (const root of searchRoots) for await (const filePath of this.jian.glob(root, args.pattern, { allowedRoots: [root] })) {
 				yielded++;
+				if (signal && yielded % 128 === 0) signal.throwIfAborted();
 				if (yielded >= YIELD_SAFETY_CAP) {
 					truncated = true;
 					break outer;
@@ -72130,16 +72277,22 @@ var GlobTool = class {
 			const pathClass = this.jian.pathClass();
 			const relBase = searchRoots[0] ?? this.workspace.workspaceDir;
 			const displayLines = paths.map((p) => relativizeIfUnder$1(p, relBase, pathClass));
-			if (entries.length === 0 && !truncated) return { output: "No matches found" };
-			const lines = [];
-			if (truncated) {
-				lines.push(`[Truncated at ${String(MAX_MATCHES)} matches — use a more specific pattern]`);
-				lines.push(`Only the first ${String(MAX_MATCHES)} matches are returned.`);
+			let output;
+			if (entries.length === 0 && !truncated) output = "No matches found";
+			else {
+				const lines = [];
+				if (truncated) {
+					lines.push(`[Truncated at ${String(MAX_MATCHES)} matches — use a more specific pattern]`);
+					lines.push(`Only the first ${String(MAX_MATCHES)} matches are returned.`);
+				}
+				lines.push(...displayLines);
+				if (!truncated && entries.length === 1e3) lines.push(`Found ${String(entries.length)} matches`);
+				output = lines.join("\n");
 			}
-			lines.push(...displayLines);
-			if (!truncated && entries.length === 1e3) lines.push(`Found ${String(entries.length)} matches`);
-			return { output: lines.join("\n") };
+			scanCache.set(searchRoots[0], args.pattern, includeDirs, output);
+			return { output };
 		} catch (error) {
+			if (signal?.aborted) throw error;
 			if (error !== null && typeof error === "object" && "code" in error) {
 				const code = error.code;
 				const path = searchRoots[0] ?? this.workspace.workspaceDir;
@@ -75416,6 +75569,85 @@ function rgUnavailableMessage(cause) {
 Error: ${cause instanceof Error ? cause.message : typeof cause === "string" ? cause : "unknown error"}\n\nFix options:\n  macOS:   brew install ripgrep\n  Ubuntu:  sudo apt-get install ripgrep\n  Other:   https://github.com/BurntSushi/ripgrep#installation\n\nAlternatively, drop a static rg binary at ${join$1(getShareDir(), "bin", rgBinaryName())}`;
 }
 //#endregion
+//#region ../../packages/agent-core/src/tools/support/rg-pattern-sanitize.ts
+/**
+* Ripgrep pattern sanitization and error detection.
+*
+* Users frequently search for code fragments that contain regex metacharacters
+* (e.g. `fetchFoo(`, `${platform}`, `a{3`). ripgrep uses the Rust `regex`
+* crate, which rejects unescaped `{`/`}` that do not form a valid repetition
+* quantifier (`{N}`, `{N,}`, `{N,M}`). This module pre-cleans such braces so
+* the common case "search for a literal-ish fragment" succeeds without a
+* syntax error.
+*
+* When sanitization is insufficient (e.g. unbalanced parentheses), the caller
+* can detect the regex error from ripgrep stderr and retry with
+* `--fixed-strings`, which treats the pattern as a literal string.
+*/
+/** Matches the inner content of a valid repetition quantifier: `N`, `N,`, `N,M`. */
+const QUANTIFIER_INNER_RE = /^\d+(?:,\d*)?$/;
+/**
+* Escape `{` and `}` that cannot form a valid repetition quantifier so they
+* are treated as literals by the regex engine.
+*
+* Already-escaped braces (`\{`, `\}`) are preserved. Valid quantifiers
+* (`{3}`, `{2,}`, `{1,5}`) are preserved. Everything else is escaped.
+*
+* Escaping braces inside character classes (e.g. `[{]`) is also safe:
+* `\{` inside `[...]` matches a literal `{` just like an unescaped `{` would.
+*/
+function sanitizeRgPattern(pattern) {
+	let result = "";
+	let i = 0;
+	while (i < pattern.length) {
+		const ch = pattern[i];
+		if (ch === "\\" && i + 1 < pattern.length) {
+			result += pattern.slice(i, i + 2);
+			i += 2;
+			continue;
+		}
+		if (ch === "{") {
+			const closeIdx = pattern.indexOf("}", i + 1);
+			if (closeIdx !== -1) {
+				const inner = pattern.slice(i + 1, closeIdx);
+				if (QUANTIFIER_INNER_RE.test(inner)) {
+					result += pattern.slice(i, closeIdx + 1);
+					i = closeIdx + 1;
+					continue;
+				}
+			}
+			result += "\\{";
+			i++;
+			continue;
+		}
+		if (ch === "}") {
+			result += "\\}";
+			i++;
+			continue;
+		}
+		result += ch;
+		i++;
+	}
+	return result;
+}
+/** Substrings that indicate ripgrep failed to parse the regex pattern. */
+const REGEX_ERROR_MARKERS = [
+	"regex parse error",
+	"unrecognized escape",
+	"unclosed group",
+	"unbalanced",
+	"unexpected repetition"
+];
+/**
+* Detect whether ripgrep's stderr indicates a regex syntax error (as opposed
+* to a filesystem or runtime error). Used to decide whether a
+* `--fixed-strings` fallback retry is worthwhile.
+*/
+function isRegexSyntaxError(stderr) {
+	const lower = stderr.toLowerCase();
+	return REGEX_ERROR_MARKERS.some((marker) => lower.includes(marker));
+}
+//#endregion
 //#region ../../packages/agent-core/src/tools/support/result-builder.ts
 const DEFAULT_MAX_CHARS = 5e4;
 const DEFAULT_TAIL_CHARS = 2e4;
@@ -75572,7 +75804,7 @@ function countLines(text) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/grep.md
-var grep_default = "Search file contents using regular expressions (powered by ripgrep).\n\nUse Grep when the task is to find unknown content or unknown file locations. Do not use shell `grep` or `rg` directly; this tool applies workspace path policy, output limits, and sensitive-file filtering.\nALWAYS use Grep tool instead of running `grep` or `rg` from a shell — direct shell calls bypass workspace policy, output limits, and sensitive-file filtering.\nIf you already know a concrete file path and need to inspect its contents, use Read directly instead.\n\nWrite patterns in ripgrep regex syntax, which differs from POSIX `grep` syntax. For example, braces are special, so escape them as `\\{` to match a literal `{`.\n\nHidden files (dotfiles such as `.gitlab-ci.yml` or `.eslintrc.json`) are searched by default. To also search files excluded by `.gitignore` (such as `node_modules` or build outputs), set `include_ignored` to `true`. Sensitive files (such as `.env`) are always skipped for safety, even when `include_ignored` is `true`.\n";
+var grep_default = "Search file contents using regular expressions (powered by ripgrep).\n\nUse Grep when the task is to find unknown content or unknown file locations. Do not use shell `grep` or `rg` directly; this tool applies workspace path policy, output limits, and sensitive-file filtering.\nALWAYS use Grep tool instead of running `grep` or `rg` from a shell - direct shell calls bypass workspace policy, output limits, and sensitive-file filtering.\n\nWrite patterns in ripgrep regex syntax, which differs from POSIX `grep` syntax. For example, braces are special, so escape them as `\\{` to match a literal `{`.\n\nHidden files (dotfiles such as `.gitlab-ci.yml` or `.eslintrc.json`) are searched by default.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/grep.ts
 const GrepInputSchema = z.object({
@@ -75640,11 +75872,12 @@ const SENSITIVE_GLOBS_TO_EXCLUDE = [
 	"**/.gcp/credentials/**"
 ];
 const CONTENT_LINE_RE = /^(.*?)([:-])(\d+)\2/;
+const GREP_DESCRIPTION = renderPrompt(grep_default, { DEFAULT_HEAD_LIMIT });
 var GrepTool = class {
 	jian;
 	workspace;
 	name = "Grep";
-	description = grep_default;
+	description = GREP_DESCRIPTION;
 	parameters = toInputJsonSchema(GrepInputSchema);
 	constructor(jian, workspace) {
 		this.jian = jian;
@@ -75701,6 +75934,15 @@ var GrepTool = class {
 			runResult = await runRipgrepOnce(this.jian, buildRgArgs(rgPath, args, searchPaths, true), signal);
 			if (runResult.kind === "tool-error") return runResult.result;
 		}
+		if (runResult.exitCode !== 0 && runResult.exitCode !== 1 && !runResult.timedOut && isRegexSyntaxError(runResult.stderrText)) {
+			const fallback = await runRipgrepOnce(this.jian, buildRgArgs(rgPath, args, searchPaths, false, true), signal);
+			if (fallback.kind === "tool-error") return fallback.result;
+			if (shouldRetryRipgrepEagain(fallback)) {
+				const retry = await runRipgrepOnce(this.jian, buildRgArgs(rgPath, args, searchPaths, true, true), signal);
+				if (retry.kind === "tool-error") return retry.result;
+				if (retry.exitCode === 0 || retry.exitCode === 1) runResult = retry;
+			} else if (fallback.exitCode === 0 || fallback.exitCode === 1) runResult = fallback;
+		}
 		const { exitCode, stderrText, bufferTruncated, stderrTruncated, timedOut } = runResult;
 		let { stdoutText } = runResult;
 		if (exitCode !== 0 && exitCode !== 1 && !timedOut) return {
@@ -75955,10 +76197,11 @@ async function mapWithConcurrency(items, concurrency, signal, mapper) {
 	if (signal.aborted) throw new GrepAbortedError();
 	return results;
 }
-function buildRgArgs(rgPath, args, searchPaths, singleThreaded = false) {
+function buildRgArgs(rgPath, args, searchPaths, singleThreaded = false, literal = false) {
 	const cmd = [rgPath];
 	if (singleThreaded) cmd.push("-j", "1");
 	cmd.push("--hidden");
+	if (literal) cmd.push("--fixed-strings");
 	const mode = args.output_mode ?? "files_with_matches";
 	if (mode !== "content") cmd.push("--max-columns", String(RG_MAX_COLUMNS));
 	cmd.push("--null");
@@ -75981,7 +76224,8 @@ function buildRgArgs(rgPath, args, searchPaths, singleThreaded = false) {
 	if (args.multiline) cmd.push("-U", "--multiline-dotall");
 	if (args.include_ignored) cmd.push("--no-ignore");
 	for (const glob of SENSITIVE_GLOBS_TO_EXCLUDE) cmd.push("--glob", `!${glob}`);
-	cmd.push("--", args.pattern, ...searchPaths);
+	const pattern = literal ? args.pattern : sanitizeRgPattern(args.pattern);
+	cmd.push("--", pattern, ...searchPaths);
 	return cmd;
 }
 function splitRgLines(text) {
@@ -76695,7 +76939,7 @@ async function partitionExistingPaths(paths, jian, workspace) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/read.md
-var read_default = "Read a text file from the local filesystem.\n\nIf the user provides a concrete file path to a text file, call Read directly. Do not `Glob`, `ls`, or otherwise pre-check known text file paths; missing or invalid file paths return errors you can handle. Do not use Read for directories; use `ls` via Bash for a known directory, or Glob when you need files/directories matching a pattern. Use `Grep` only when the task is to search for unknown content or locations.\n\nWhen you need several files, prefer to read them in parallel: emit multiple `Read` calls in a single response instead of reading one file per turn.\n\n- Relative paths resolve against the working directory; a path outside the working directory must be absolute.\n- Returns up to {{ MAX_LINES }} lines or {{ MAX_BYTES_KB }} KB per call, whichever comes first; lines longer than {{ MAX_LINE_LENGTH }} chars are truncated mid-line.\n- Page larger files with `line_offset` (1-based start line) and `n_lines`. Omit `n_lines` to read up to the {{ MAX_LINES }}-line cap.\n- Sensitive files (`.env` files, credential stores, SSH keys, and similar secrets) are refused to protect secrets; do not attempt to read them.\n- Only UTF-8 text files can be read. Non-UTF-8 encodings, binary files, and files containing NUL bytes are refused; use `ReadMediaFile` for images or video, and Bash or an MCP tool for other binary formats.\n- Negative line_offset reads from the end of the file (for example, -100 reads the last 100 lines); the absolute value cannot exceed {{ MAX_LINES }}.\n- Output format: `<line-number>\\t<content>` per line.\n- A `<system>...</system>` status block is appended after the file content; it summarizes how much was read (line and byte counts, truncation, line-ending notes) and is not part of the file itself. The status block includes an `Anchor: <hash>` value that can be passed to `Edit.anchor` to verify the file has not changed before editing.\n- Pure CRLF files are displayed with LF line endings; `Edit` matches this output and preserves CRLF when writing back.\n- Mixed or lone carriage-return line endings are shown as `\\r` and require exact `Edit.old_string` escapes.\n- After a successful `Edit`/`Write`, do not re-read solely to prove the write landed. When the task depends on an exact file, API, or output shape, inspect the final external contract before finishing.\n";
+var read_default = "Read a text file from the local filesystem.\n\nIf the user provides a concrete file path to a text file, call Read directly. Do not `Glob`, `ls`, or otherwise pre-check known text file paths; missing or invalid file paths return errors you can handle. Do not use Read for directories; use `ls` via Bash for a known directory, or Glob when you need files/directories matching a pattern. Use `Grep` only when the task is to search for unknown content or locations.\n\nWhen you need several files, prefer to read them in parallel: emit multiple `Read` calls in a single response instead of reading one file per turn.\n\n- Returns up to {{ MAX_BYTES_KB }} KB per call; lines longer than {{ MAX_LINE_LENGTH }} chars are truncated mid-line.\n- Sensitive files (`.env` files, credential stores, SSH keys, and similar secrets) are refused to protect secrets; do not attempt to read them.\n- Only UTF-8 text files can be read. Non-UTF-8 encodings, binary files, and files containing NUL bytes are refused; use `ReadMediaFile` for images or video, and Bash or an MCP tool for other binary formats.\n- Output format: `<line-number>\\t<content>` per line.\n- A `<system>...</system>` status block is appended after the file content; it summarizes how much was read (line and byte counts, truncation, line-ending notes) and is not part of the file itself. The status block includes an `Anchor: <hash>` value that can be passed to `Edit.anchor` to verify the file has not changed before editing.\n- Pure CRLF files are displayed with LF line endings; `Edit` matches this output and preserves CRLF when writing back.\n- Mixed or lone carriage-return line endings are shown as `\\r` and require exact `Edit.old_string` escapes.\n- After a successful `Edit`/`Write`, do not re-read solely to prove the write landed. When the task depends on an exact file, API, or output shape, inspect the final external contract before finishing.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/read.ts
 const MAX_LINES = 1e3;
@@ -77051,7 +77295,7 @@ var ReadTool = class {
 		if (input.maxLinesReached) parts.push(`Max ${String(MAX_LINES)} lines reached.`);
 		else if (input.maxBytesReached) parts.push(`Max ${String(MAX_BYTES)} bytes reached.`);
 		else if (lineCount < input.requestedLines) parts.push("End of file reached.");
-		if (input.truncatedLineNumbers.length > 0) parts.push(`Lines [${input.truncatedLineNumbers.join(", ")}] were truncated.`);
+		if (input.truncatedLineNumbers.length > 0) parts.push(`Lines [${input.truncatedLineNumbers.join(", ")}] exceed the ${String(MAX_LINE_LENGTH)}-char limit and were truncated. Re-read with line_offset and n_lines=1 to view individual long lines in full.`);
 		if (input.lineEndingStyle === "mixed") parts.push("Mixed or lone carriage-return line endings are shown as \\r. Use exact \\r\\n or \\r escapes in Edit.old_string for those lines.");
 		parts.push(`Anchor: ${input.anchor}`);
 		return parts.join(" ");
@@ -77450,7 +77694,7 @@ var ReadMediaFileTool = class {
 };
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/write.md
-var write_default = "Overwrite or append to a file with content exactly as provided, creating the file if needed; the parent directory must already exist. Defaults to overwrite; append adds content to the end without adding a newline. Write does not use the Read/Edit model text view and does not preserve or infer the previous line-ending style: \\n stays LF, \\r\\n stays CRLF. Use Edit for targeted changes to existing files. When the content is very large, you can split it across multiple calls: write the first chunk with overwrite, then add the remaining chunks with append. Write refuses content containing `<<<<<<<`/`=======`/`>>>>>>>` merge conflict markers — resolve conflicts first.\n";
+var write_default = "Write does not preserve or infer the previous line-ending style: \\n stays LF, \\r\\n stays CRLF. Use Edit for targeted changes to existing files. When the content is very large, you can split it across multiple calls: write the first chunk with overwrite, then add the remaining chunks with append. Write refuses content containing `<<<<<<<`/`=======`/`>>>>>>>` merge conflict markers - resolve conflicts first.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/file/write.ts
 /** Mask isolating the file-type bits of a stat mode. */
@@ -77498,10 +77742,11 @@ var WriteTool = class {
 				pathClass: this.jian.pathClass(),
 				homeDir: this.jian.gethome()
 			}),
-			execute: () => this.execution(args, path)
+			execute: ({ signal }) => this.execution(args, path, signal)
 		};
 	}
-	async execution(args, safePath) {
+	async execution(args, safePath, signal) {
+		signal?.throwIfAborted();
 		const parentError = await this.checkParentDirectory(safePath);
 		if (parentError !== void 0) return {
 			isError: true,
@@ -77516,6 +77761,7 @@ var WriteTool = class {
 			const mode = args.mode ?? "overwrite";
 			if (mode === "append") await this.jian.writeText(safePath, args.content, { mode: "a" });
 			else await this.jian.writeText(safePath, args.content);
+			scanCache.clear();
 			const bytesWritten = Buffer.byteLength(args.content, "utf8");
 			const { notice, hasErrors } = await this.appendDiagnostics(safePath);
 			const output = `${mode === "append" ? "Appended" : "Wrote"} ${String(bytesWritten)} bytes to ${args.path}${notice}`;
@@ -77565,7 +77811,7 @@ var WriteTool = class {
 };
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/planning/enter-plan-mode.md
-var enter_plan_mode_default = "Use this tool proactively when you're about to start a non-trivial implementation task.\nGetting user sign-off on your approach via ExitPlanMode before writing code prevents wasted effort.\n\n## Planning Modes\n\nThe host supports two planning strategies. You can request either one via this tool:\n\n- **Normal plan** (default): You investigate the codebase, design a single implementation approach, write it to the plan file, and present it for approval. Best when the task is straightforward or you are already confident about the right approach.\n- **Fusion plan**: Invoke the FusionPlan tool to spawn multiple independent planning subagents in parallel, each exploring a different angle, then synthesize their outputs into one consolidated plan. Best when the task is ambiguous, has many valid approaches, crosses many files, or when exploration itself adds significant value. Fusion plan may take longer but tends to surface risks and alternatives you might miss.\n\nTo request a fusion plan, include `mode: 'fusion'` in your tool arguments. When in fusion strategy, call the FusionPlan tool to generate the plan.\n\n### When to choose which mode\n\nPrefer **normal plan** when:\n1. The user gave specific, detailed instructions.\n2. The change is small or localized (1-3 files, single concern).\n3. You are confident about the codebase structure and the right approach.\n4. Speed matters more than exploring alternatives.\n\nPrefer **fusion plan** when:\n1. The task is open-ended or ambiguous (e.g. \"improve performance\", \"refactor auth\").\n2. Multiple valid architectures or approaches exist.\n3. The change spans more than 3-5 files or touches core abstractions.\n4. You are unfamiliar with the relevant code paths and want parallel exploration.\n5. The user explicitly asked for a thorough plan or mentioned comparing options.\n\nIf unsure, choose normal plan for small fixes and fusion plan for larger design tasks.\n\n## When to Use\n\nUse this tool when ANY of these conditions apply:\n\n1. New Feature Implementation - e.g. \"Add a caching layer to the API\"\n2. Multiple Valid Approaches - e.g. \"Optimize database queries\" (indexing vs rewrite vs caching)\n3. Code Modifications - e.g. \"Refactor auth module to support OAuth\"\n4. Architectural Decisions - e.g. \"Add WebSocket support\"\n5. Multi-File Changes - involves more than 2-3 files\n6. Unclear Requirements - need exploration to understand scope\n7. User Preferences Matter - if user input would materially change the implementation approach, use EnterPlanMode to structure the decision\n\nPermission mode notes:\n- EnterPlanMode enters plan mode automatically without an approval prompt in all permission modes.\n- In yolo and manual modes, ExitPlanMode still presents the plan to the user for approval.\n- In auto permission mode, do not use AskUserQuestion; make the best decision from available context.\n- In auto permission mode, ExitPlanMode exits plan mode without asking the user.\n- Use EnterPlanMode only when planning itself adds value.\n\nWhen NOT to use:\n- Single-line or few-line fixes (typos, obvious bugs, small tweaks)\n- User gave very specific, detailed instructions\n- Pure research/exploration tasks\n\n## What Happens in Plan Mode\nIn plan mode, you will:\n1. Identify 2-3 key questions about the codebase that are critical to your plan. If you are not confident about the codebase structure or relevant code paths, use `Agent(subagent_type=\"explore\")` to investigate these questions first - this is strongly recommended for non-trivial tasks.\n2. Explore the codebase using Glob, Grep, Read, and other read-only tools for any remaining quick lookups. Use Bash only when needed; Bash follows the normal permission mode and rules.\n3. Design an implementation approach based on your findings (or, for fusion plan, call FusionPlan to generate the synthesized plan).\n4. Review the generated plan, fill in any gaps, and ensure it matches the user's intent.\n5. Present your plan to the user via ExitPlanMode for approval\n\nFor fusion plan, the FusionPlan tool performs the parallel exploration and synthesis for you; you should still review the result before exiting plan mode.\n";
+var enter_plan_mode_default = "Use this tool proactively when you're about to start a non-trivial implementation task.\nGetting user sign-off on your approach via ExitPlanMode before writing code prevents wasted effort.\n\n## Planning Modes\n\n- **Normal plan**: You investigate the codebase, design a single approach, write it to the plan file, and present it for approval.\n- **Fusion plan**: Invoke the FusionPlan tool to spawn parallel planning subagents, each exploring a different angle, then synthesize their outputs into one plan. Fusion plan may take longer but tends to surface risks and alternatives you might miss.\n\n### When to choose which mode\n\nPrefer **normal plan** when:\n1. The user gave specific, detailed instructions.\n2. The change is small or localized (1-3 files, single concern).\n3. You are confident about the codebase structure and the right approach.\n4. Speed matters more than exploring alternatives.\n\nPrefer **fusion plan** when:\n1. The task is open-ended or ambiguous (e.g. \"improve performance\", \"refactor auth\").\n2. Multiple valid architectures or approaches exist.\n3. The change spans more than 3-5 files or touches core abstractions.\n4. You are unfamiliar with the relevant code paths and want parallel exploration.\n5. The user explicitly asked for a thorough plan or mentioned comparing options.\n\nIf unsure, choose normal plan for small fixes and fusion plan for larger design tasks.\n\n## When to Use\n\nUse this tool when ANY of these conditions apply:\n\n1. New Feature Implementation - e.g. \"Add a caching layer to the API\"\n2. Multiple Valid Approaches - e.g. \"Optimize database queries\" (indexing vs rewrite vs caching)\n3. Code Modifications - e.g. \"Refactor auth module to support OAuth\"\n4. Architectural Decisions - e.g. \"Add WebSocket support\"\n5. Multi-File Changes - involves more than 2-3 files\n6. Unclear Requirements - need exploration to understand scope\n7. User Preferences Matter - if user input would materially change the implementation approach, use EnterPlanMode to structure the decision\n\nPermission mode notes:\n- EnterPlanMode enters plan mode automatically without an approval prompt in all permission modes.\n- In yolo and manual modes, ExitPlanMode still presents the plan to the user for approval.\n- In auto permission mode, do not use AskUserQuestion; make the best decision from available context.\n- In auto permission mode, ExitPlanMode exits plan mode without asking the user.\n- Use EnterPlanMode only when planning itself adds value.\n\nWhen NOT to use:\n- Single-line or few-line fixes (typos, obvious bugs, small tweaks)\n- User gave very specific, detailed instructions\n- Pure research/exploration tasks\n\n## What Happens in Plan Mode\nIn plan mode, you will:\n1. Identify 2-3 key questions about the codebase that are critical to your plan. If you are not confident about the codebase structure or relevant code paths, use `Agent(subagent_type=\"explore\")` to investigate these questions first - this is strongly recommended for non-trivial tasks.\n2. Explore the codebase using Glob, Grep, Read, and other read-only tools for any remaining quick lookups. Use Bash only when needed; Bash follows the normal permission mode and rules.\n3. Design an implementation approach based on your findings (or, for fusion plan, call FusionPlan to generate the synthesized plan).\n4. Review the generated plan, fill in any gaps, and ensure it matches the user's intent.\n5. Present your plan to the user via ExitPlanMode for approval\n\nFor fusion plan, the FusionPlan tool performs the parallel exploration and synthesis for you; you should still review the result before exiting plan mode.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/planning/enter-plan-mode.ts
 const EnterPlanModeInputSchema = z.object({ mode: z.enum(["normal", "fusion"]).default("normal").describe("Planning strategy. 'normal' (default): you design the plan. 'fusion': the host spawns parallel planning subagents and synthesizes a single plan for you to review. Use 'fusion' for ambiguous, large, or multi-approach tasks.") }).strict();
@@ -77650,7 +77896,7 @@ function enteredPlanModeMessage(mode, planPath) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/planning/exit-plan-mode.md
-var exit_plan_mode_default = "Use this tool when you are in plan mode and have finished writing your plan to the plan file and are ready for user approval.\n\n## How This Tool Works\n- You should have already written your plan to the plan file specified in the plan mode reminder.\n- This tool does NOT take the plan content as a parameter - it reads the plan from the file you wrote.\n- The user will see the contents of your plan file when they review it. In auto permission mode, the tool reads the file and exits plan mode without asking the user.\n\n## When to Use\nOnly use this tool for tasks that require planning implementation steps. For research tasks (searching files, reading code, understanding the codebase), do NOT use this tool.\n\n## Multiple Approaches\nIf your plan contains multiple alternative approaches:\n- Pass them via the `options` parameter so the user can choose which approach to execute.\n- Each option should have a concise label and a brief description of trade-offs.\n- If you recommend one option, append \"(Recommended)\" to its label.\n- In yolo and manual modes, the user will see all options alongside Reject and Revise choices.\n- Provide up to 3 options; the host adds the standard rejection and revision controls. When the plan offers a real choice, 2-3 distinct approaches work best.\n- Passing a single option is allowed and is equivalent to a plain plan approval (no approach choice is surfaced to the user).\n- Do NOT use \"Reject\", \"Reject and Exit\", \"Revise\", or \"Approve\" as option labels - these are reserved by the system.\n\n## Before Using\n- In auto permission mode, do NOT use AskUserQuestion; make the best decision from available context.\n- In auto permission mode, this tool exits plan mode without asking the user.\n- In yolo and manual modes, this tool still presents the plan to the user for approval.\n- If auto permission mode is not active and you have unresolved questions, use AskUserQuestion first.\n- If auto permission mode is not active and you have multiple approaches and haven't narrowed down yet, consider using AskUserQuestion first to let the user choose, then write a plan for the chosen approach only.\n- Once your plan is finalized, use THIS tool to request approval.\n- Do NOT use AskUserQuestion to ask \"Is this plan OK?\" or \"Should I proceed?\" - that is exactly what ExitPlanMode does.\n- If rejected, revise based on feedback and call ExitPlanMode again.\n";
+var exit_plan_mode_default = "Use this tool when you are in plan mode and have finished writing your plan to the plan file and are ready for user approval.\n\n## How This Tool Works\n- You should have already written your plan to the plan file specified in the plan mode reminder.\n- This tool does NOT take the plan content as a parameter - it reads the plan from the file you wrote.\n- The user will see the contents of your plan file when they review it. In auto permission mode, the tool reads the file and exits plan mode without asking the user.\n\n## When to Use\nOnly use this tool for tasks that require planning implementation steps. For research tasks (searching files, reading code, understanding the codebase), do NOT use this tool.\n\n## Multiple Approaches\nIf your plan contains multiple alternative approaches:\n- If you recommend one option, append \"(Recommended)\" to its label.\n- In yolo and manual modes, the user will see all options alongside Reject and Revise choices.\n- Passing a single option is allowed and is equivalent to a plain plan approval (no approach choice is surfaced to the user).\n\n## Before Using\n- In auto permission mode, do NOT use AskUserQuestion; make the best decision from available context.\n- In auto permission mode, this tool exits plan mode without asking the user.\n- In yolo and manual modes, this tool still presents the plan to the user for approval.\n- If auto permission mode is not active and you have unresolved questions, use AskUserQuestion first.\n- If auto permission mode is not active and you have multiple approaches and haven't narrowed down yet, consider using AskUserQuestion first to let the user choose, then write a plan for the chosen approach only.\n- Once your plan is finalized, use THIS tool to request approval.\n- Do NOT use AskUserQuestion to ask \"Is this plan OK?\" or \"Should I proceed?\" - that is exactly what ExitPlanMode does.\n- If rejected, revise based on feedback and call ExitPlanMode again.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/planning/exit-plan-mode.ts
 const RESERVED_OPTION_LABELS = new Set([
@@ -80019,7 +80265,9 @@ var MicroCompaction = class {
 		const nextCutoff = computeCutoff(history, config);
 		if (nextCutoff <= this.cutoff) return;
 		const { beforeTokens, afterTokens } = this.measureEffect(history, nextCutoff);
-		if (beforeTokens - afterTokens < config.pruneMinReclaimTokens) return;
+		const reclaimTokens = beforeTokens - afterTokens;
+		if (reclaimTokens < config.pruneMinReclaimTokens) return;
+		if (estimateTokensForMessages(history.slice(nextCutoff)) * 1.15 > reclaimTokens) return;
 		this.apply(nextCutoff);
 	}
 	/**
@@ -81515,22 +81763,38 @@ function toolResultOutputForModel(result) {
 	}, ...truncateContentParts(output)];
 	return truncateContentParts(output);
 }
-/** Truncate a plain-text tool output that exceeds MAX_TOOL_RESULT_TOKENS. */
+/** Truncate a plain-text tool output that exceeds MAX_TOOL_RESULT_TOKENS.
+*  Tail-biased: keeps 25% head + 75% tail so error messages and test
+*  failures (usually at the end) survive truncation. */
 function truncateToolOutput(text) {
 	if (estimateTokens$1(text) <= MAX_TOOL_RESULT_TOKENS) return text;
 	const budget = MAX_TOOL_RESULT_TOKENS - estimateTokens$1(TOOL_TRUNCATION_NOTICE);
 	if (budget <= 0) return TOOL_TRUNCATION_NOTICE.trim();
-	let kept = "";
-	let tokens = 0;
+	const headBudget = Math.floor(budget * .25);
+	const tailBudget = budget - headBudget;
+	let head = "";
+	let headTokens = 0;
 	for (const ch of text) {
 		const chTokens = ch.codePointAt(0) <= 127 ? 1 / 4 : 1;
-		if (tokens + chTokens > budget) break;
-		kept += ch;
-		tokens += chTokens;
+		if (headTokens + chTokens > headBudget) break;
+		head += ch;
+		headTokens += chTokens;
+	}
+	const reversed = [...text].toReversed();
+	const tailChars = [];
+	let tailTokens = 0;
+	for (const ch of reversed) {
+		const chTokens = ch.codePointAt(0) <= 127 ? 1 / 4 : 1;
+		if (tailTokens + chTokens > tailBudget) break;
+		tailChars.push(ch);
+		tailTokens += chTokens;
 	}
-	return kept + TOOL_TRUNCATION_NOTICE;
+	const tail = tailChars.toReversed().join("");
+	const notice = `\n[content truncated - ~${Math.max(0, Math.round(estimateTokens$1(text) - headTokens - tailTokens))} tokens omitted]\n`;
+	return head + notice + tail;
 }
-/** Truncate oversized text parts in a ContentPart array. */
+/** Truncate oversized text parts in a ContentPart array.
+*  Tail-biased: keeps 25% head + 75% tail. */
 function truncateContentParts(parts) {
 	let totalTokens = 0;
 	for (const p of parts) if (p.type === "text") totalTokens += estimateTokens$1(p.text);
@@ -81540,39 +81804,83 @@ function truncateContentParts(parts) {
 		type: "text",
 		text: TOOL_TRUNCATION_NOTICE.trim()
 	}];
-	const result = [];
-	let used = 0;
-	for (const p of parts) {
+	const headBudget = Math.floor(budget * .25);
+	const tailBudget = budget - headBudget;
+	const headParts = [];
+	let headUsed = 0;
+	let headEnd = 0;
+	for (let i = 0; i < parts.length; i++) {
+		const p = parts[i];
 		if (p.type !== "text") {
-			result.push(p);
+			headParts.push(p);
+			headEnd = i + 1;
 			continue;
 		}
 		const partTokens = estimateTokens$1(p.text);
-		if (used + partTokens <= budget) {
-			result.push(p);
-			used += partTokens;
+		if (headUsed + partTokens <= headBudget) {
+			headParts.push(p);
+			headUsed += partTokens;
+			headEnd = i + 1;
 		} else {
-			const remaining = budget - used;
-			let kept = "";
-			let t = 0;
-			for (const ch of p.text) {
-				const chTokens = ch.codePointAt(0) <= 127 ? 1 / 4 : 1;
-				if (t + chTokens > remaining) break;
-				kept += ch;
-				t += chTokens;
-			}
-			if (kept.length > 0) result.push({
-				type: "text",
-				text: kept
-			});
+			const remaining = headBudget - headUsed;
+			if (remaining > 0) {
+				let kept = "";
+				let t = 0;
+				for (const ch of p.text) {
+					const chTokens = ch.codePointAt(0) <= 127 ? 1 / 4 : 1;
+					if (t + chTokens > remaining) break;
+					kept += ch;
+					t += chTokens;
+				}
+				if (kept.length > 0) headParts.push({
+					type: "text",
+					text: kept
+				});
+			}
 			break;
 		}
 	}
-	result.push({
-		type: "text",
-		text: TOOL_TRUNCATION_NOTICE
-	});
-	return result;
+	const tailParts = [];
+	let tailUsed = 0;
+	for (let i = parts.length - 1; i >= headEnd; i--) {
+		const p = parts[i];
+		if (p.type !== "text") {
+			tailParts.unshift(p);
+			continue;
+		}
+		const partTokens = estimateTokens$1(p.text);
+		if (tailUsed + partTokens <= tailBudget) {
+			tailParts.unshift(p);
+			tailUsed += partTokens;
+		} else {
+			const remaining = tailBudget - tailUsed;
+			if (remaining > 0) {
+				const chars = [...p.text];
+				let kept = "";
+				let t = 0;
+				for (let j = chars.length - 1; j >= 0; j--) {
+					const chTokens = chars[j].codePointAt(0) <= 127 ? 1 / 4 : 1;
+					if (t + chTokens > remaining) break;
+					kept = chars[j] + kept;
+					t += chTokens;
+				}
+				if (kept.length > 0) tailParts.unshift({
+					type: "text",
+					text: kept
+				});
+			}
+			break;
+		}
+	}
+	const omitted = Math.max(0, Math.round(totalTokens - headUsed - tailUsed));
+	return [
+		...headParts,
+		{
+			type: "text",
+			text: `[content truncated - ~${omitted} tokens omitted]`
+		},
+		...tailParts
+	];
 }
 function isEmptyOutputText(output) {
 	return output.length === 0 || output.trim() === TOOL_OUTPUT_EMPTY_TEXT;
@@ -123450,7 +123758,7 @@ function optionalBuildString(value) {
 	return typeof value === "string" && value.length > 0 ? value : void 0;
 }
 const SCREAM_BUILD_INFO = {
-	version: optionalBuildString("0.10.8"),
+	version: optionalBuildString("0.10.9"),
 	channel: optionalBuildString(""),
 	commit: optionalBuildString(""),
 	buildTarget: optionalBuildString("darwin-arm64")
@@ -126747,6 +127055,30 @@ function formatFooterGitBadge(status, colors) {
 	if (status.pullRequest === null) return base;
 	return `${base} ${chalk.hex(colors.primary)(formatPullRequestBadge(status.pullRequest, { linkPullRequest: true }))}`;
 }
+/**
+* Middle-truncate a (possibly ANSI-colored) string to `maxWidth` visible
+* columns, keeping a head and a tail fragment joined by `ellipsis`. The
+* remaining budget is split roughly in half so both the start and the end of
+* the original content stay visible - e.g. `GOAL 3m · 7 turns` becomes
+* `GOAL… turns` (head `GOAL`, tail `turns`). ANSI styling is preserved via
+* sliceByColumn, which carries the active SGR state into the tail; a reset is
+* emitted around the ellipsis so a colour opened in the head never bleeds
+* across it. Exported for unit testing.
+*/
+function truncateMiddle(line, maxWidth, ellipsis) {
+	if (maxWidth <= 0) return "";
+	const textWidth = visibleWidth(line);
+	if (textWidth <= maxWidth) return line;
+	const ellipsisWidth = visibleWidth(ellipsis);
+	if (ellipsisWidth >= maxWidth) return truncateToWidth(line, maxWidth, ellipsis);
+	const keepWidth = maxWidth - ellipsisWidth;
+	const headWidth = Math.max(0, Math.ceil(keepWidth / 2));
+	const tailWidth = keepWidth - headWidth;
+	const head = headWidth > 0 ? sliceByColumn(line, 0, headWidth) : "";
+	const tail = tailWidth > 0 ? sliceByColumn(line, textWidth - tailWidth, tailWidth) : "";
+	const RESET = "\x1B[0m";
+	return head + RESET + ellipsis + RESET + tail;
+}
 var FooterComponent = class {
 	state;
 	colors;
@@ -126855,13 +127187,21 @@ var FooterComponent = class {
 		}
 		const rightWidth = visibleWidth(rightText);
 		const gap = 3;
+		const ellipsis = chalk.hex(colors.textDim)("…");
 		let line1;
 		if (leftWidth + gap + rightWidth <= width) {
 			const pad = width - leftWidth - rightWidth;
 			line1 = leftLine + " ".repeat(pad) + rightText;
-		} else if (leftWidth <= width) line1 = leftLine;
-		else line1 = truncateToWidth(leftLine, width, "…");
-		return [truncateToWidth(line1, width)];
+		} else {
+			const targetLeft = width - gap - rightWidth;
+			if (targetLeft > 0) {
+				const shrunkLeft = truncateMiddle(leftLine, targetLeft, ellipsis);
+				const pad = width - visibleWidth(shrunkLeft) - rightWidth;
+				line1 = shrunkLeft + " ".repeat(pad) + rightText;
+			} else if (leftWidth <= width) line1 = leftLine + " ".repeat(width - leftWidth);
+			else line1 = truncateMiddle(leftLine, width, ellipsis);
+		}
+		return [truncateToWidth(line1, width, "…")];
 	}
 };
 //#endregion
@@ -128874,7 +129214,7 @@ async function guidedGoalSetup(host) {
 		host.showNotice(t("goal.storm_breaker"), t("goal.conflict_loop"));
 		return;
 	}
-	const { TextInputDialogComponent } = await import("./text-input-dialog-B_rgO4qn.mjs");
+	const { TextInputDialogComponent } = await import("./text-input-dialog-B1ak519Y.mjs");
 	const initialDesc = await promptText(host, TextInputDialogComponent, {
 		title: t("goal.setup_title_initial"),
 		subtitle: t("goal.setup_desc_hint"),
@@ -128901,7 +129241,7 @@ async function guidedGoalSetup(host) {
 	await showGoalConfigWizard(host, session, confirmed.trim() || objective, false);
 }
 async function showGoalConfigWizard(host, session, objective, replace) {
-	const { TextInputDialogComponent } = await import("./text-input-dialog-B_rgO4qn.mjs");
+	const { TextInputDialogComponent } = await import("./text-input-dialog-B1ak519Y.mjs");
 	const turnInput = await promptNumber(host, TextInputDialogComponent, {
 		title: t("goal.wizard_title", { objective }),
 		subtitle: t("goal.budget_turns_hint"),
@@ -130301,6 +130641,18 @@ function makeDiffStyles(colors) {
 	};
 }
 const ANSI_RE = /\u001B\[[0-9;]*m/;
+const ANSI_RESET_RE = /\u001B\[(?:0|39)m/g;
+/**
+* Extract the leading ANSI SGR prefix a chalk-style color function applies,
+* e.g. `\x1b[38;2;121;235;0m` for a truecolor hex. Returns `''` when the
+* function emits no color (chalk level 0 / non-color environment).
+*/
+function extractAnsiPrefix(fn) {
+	const sentinel = "\0";
+	const styled = fn(sentinel);
+	const idx = styled.indexOf(sentinel);
+	return idx >= 0 ? styled.slice(0, idx) : "";
+}
 /** Visualize leading whitespace: tabs as `->`, leading spaces as `·`. */
 function visualizeIndent(line) {
 	let i = 0;
@@ -130330,6 +130682,11 @@ function visualizeIndent(line) {
 * runs on the raw code first; indent visualization then runs on the
 * highlighted string - leading whitespace carries no token color, so it is
 * still plain and can be replaced and dimmed without disturbing the tokens.
+*
+* When highlighting is on and produced token colors, the diff line color is
+* layered as the base foreground: syntax tokens override it, but every ANSI
+* reset re-injects the diff color so non-token spans (punctuation, operators,
+* whitespace) stay green/red instead of falling back to the terminal default.
 * When highlighting is off (streaming) or produced no token colors, the code
 * part is colored with the diff line color instead.
 */
@@ -130338,7 +130695,11 @@ function renderDiffCode(code, colorFn, highlight, lang) {
 	const indent = text.slice(0, indentEnd);
 	const rest = text.slice(indentEnd);
 	const dimIndent = indent.length > 0 ? chalk.dim(indent) : indent;
-	if (highlight && ANSI_RE.test(rest)) return dimIndent + rest;
+	if (highlight && ANSI_RE.test(rest)) {
+		const prefix = extractAnsiPrefix(colorFn);
+		if (prefix.length > 0) return dimIndent + prefix + rest.replace(ANSI_RESET_RE, (m) => m + prefix) + "\x1B[39m";
+		return dimIndent + rest;
+	}
 	return dimIndent + colorFn(rest);
 }
 /**
@@ -130765,34 +131126,43 @@ function truncateTailBytes(text, maxBytes) {
 }
 /**
 * Component that renders tool output with wrap-aware line truncation.
-* Uses pi-tui's Text component to compute actual visual wrapped lines,
-* then caps at PREVIEW_LINES. This handles long single-line output (e.g.
-* JSON blobs) that would otherwise wrap to dozens of visual rows.
+* Uses pi-tui's Text component to compute actual visual wrapped lines, then
+* caps at `maxLines`. When collapsed the TAIL is shown (newest output, where
+* command errors land) with an expand hint at the top; when expanded the full
+* output is shown with a collapse hint at the top. Handles long single-line
+* output (e.g. JSON blobs) that would otherwise wrap to dozens of visual rows.
 */
 var TruncatedOutputComponent = class {
 	textComponent;
 	expanded;
 	maxLines;
 	hintFormatter;
+	collapseHintFormatter;
 	constructor(output, options) {
 		this.expanded = options.expanded;
 		this.maxLines = options.maxLines ?? PREVIEW_LINES;
 		this.hintFormatter = options.hintFormatter;
+		this.collapseHintFormatter = options.collapseHintFormatter;
 		const tint = options.isError ? chalk.hex(options.colors.error) : chalk.dim;
 		const cleaned = trimTrailingEmptyLines(output.split("\n")).join("\n");
-		const truncated = options.maxBytes === void 0 ? cleaned : truncateTailBytes(cleaned, options.maxBytes);
-		this.textComponent = new Text(tint(truncated), 2, 0);
+		const stripped = options.isError ? cleaned.replaceAll(/\u001B\[[0-9;]*m/g, "") : cleaned;
+		const tinted = (options.maxBytes === void 0 ? stripped : truncateTailBytes(stripped, options.maxBytes)).split("\n").map((line) => tint(line)).join("\n");
+		this.textComponent = new Text(tinted, 2, 0);
 	}
 	invalidate() {
 		this.textComponent.invalidate();
 	}
 	render(width) {
 		const contentLines = this.textComponent.render(width);
-		if (this.expanded || contentLines.length <= this.maxLines) return contentLines;
-		const shown = contentLines.slice(0, this.maxLines);
+		if (contentLines.length <= this.maxLines) return contentLines;
+		if (this.expanded) {
+			const collapseHint = this.collapseHintFormatter ? this.collapseHintFormatter() : t("shell.collapse_hint");
+			return [chalk.dim(collapseHint), ...contentLines];
+		}
 		const remaining = contentLines.length - this.maxLines;
-		const hint = this.hintFormatter ? this.hintFormatter(remaining) : `... (${String(remaining)} more lines, ctrl+o to expand)`;
-		return [...shown, chalk.dim(hint)];
+		const tail = contentLines.slice(-this.maxLines);
+		const expandHint = this.hintFormatter ? this.hintFormatter(remaining) : t("shell.more_lines", { count: String(remaining) });
+		return [chalk.dim(expandHint), ...tail];
 	}
 };
 const renderTruncated = (_toolCall, result, ctx) => {
@@ -130809,7 +131179,7 @@ var ShellExecutionComponent = class extends Container {
 	constructor(options) {
 		super();
 		if (options.showCommand === true) this.addCommandPreview(options.command ?? "", options.commandPreviewLines);
-		if (options.result !== void 0) this.addResultPreview(options.result, options.colors, options.expanded ?? false, options.resultPreviewLines ?? PREVIEW_LINES);
+		if (options.result !== void 0) this.addResultPreview(options.result, options.colors, options.expanded ?? false, options.resultPreviewLines ?? 15);
 	}
 	addCommandPreview(command, previewLines) {
 		if (command.length === 0) return;
@@ -130828,7 +131198,8 @@ var ShellExecutionComponent = class extends Container {
 			colors,
 			maxLines: previewLines,
 			maxBytes: MAX_SHELL_OUTPUT_BYTES,
-			hintFormatter: (remaining) => t("shell.more_lines", { count: String(remaining) })
+			hintFormatter: (remaining) => t("shell.more_lines", { count: String(remaining) }),
+			collapseHintFormatter: () => t("shell.collapse_hint")
 		}));
 	}
 };
@@ -139051,6 +139422,8 @@ var SessionEventHandler = class {
 		this.host.showNotice(title, detail);
 	}
 	handleStepRetrying(event) {
+		this.host.streamingUI.resetLiveText();
+		this.host.streamingUI.resetToolUi();
 		this.host.setAppState({ reconnectAttempt: event.nextAttempt });
 	}
 	maybeShowDebugTiming(event) {
@@ -147665,6 +148038,7 @@ var ScreamTUI = class {
 	deferUserMessages = false;
 	aborted = false;
 	isShuttingDown = false;
+	tightModeHandler = null;
 	reverseRpcDisposers = [];
 	startupNotice;
 	updatePrefetched;
@@ -147761,6 +148135,11 @@ var ScreamTUI = class {
 		this.inputController.setupAutocomplete();
 	}
 	async start() {
+		this.tightModeHandler = () => {
+			setTightMode((process.stdout.columns ?? 80) < 60);
+		};
+		this.tightModeHandler();
+		process.stdout.on("resize", this.tightModeHandler);
 		this.lifecycleController.installSignalHandlers();
 		try {
 			const shouldReplayHistory = await this.initMainTui();
@@ -147838,6 +148217,11 @@ var ScreamTUI = class {
 	async stop(exitCode) {
 		if (this.isShuttingDown) return;
 		this.isShuttingDown = true;
+		if (this.tightModeHandler !== null) {
+			process.stdout.off("resize", this.tightModeHandler);
+			this.tightModeHandler = null;
+		}
+		setTightMode(false);
 		this.lifecycleController.stopCcConnectPolling();
 		this.lifecycleController.uninstallSignalHandlers();
 		this.aborted = true;