scream-code 0.18.5 → 0.18.6

package/dist/{dispatch-BFsePVX6.mjs → dispatch-BgO7wAf9.mjs}

@@ -6,7 +6,7 @@ const __dirname = __cjsShimDirname(__filename);
 import { i as __require, o as __toESM, r as __exportAll, t as __commonJSMin } from "./chunk-D90kvbyJ.mjs";
 import { A as sharedMemoStore, B as buildProjectTagCloud, C as applyConsolidation, D as parseMemoryMemos, E as buildExitExtractionPrompt, F as probeLocalEmbeddingSupport, G as join$1, H as basename$1, I as createMemoryMemo, J as relative$1, K as normalize, L as toSummary, M as clearEmbeddingModelCache, N as createFastEmbedEngine, O as stripMemoryTags, P as hasEmbeddingModelCache$1, R as generateTags, S as DreamTracker, T as EXIT_EXTRACTION_SYSTEM_PROMPT, U as dirname$2, V as rankMemos, W as isAbsolute$1, Y as resolve$2, a as isSupportedFile, b as sharedKnowledgeStoreReady, i as ingestFile, j as classifyEmbeddingFailure, k as MemoryMemoStore, q as parse$7, r as ingestDirectory, t as multiSearch, w as buildConsolidationPlan, y as sharedKnowledgeStore, z as normalizeTags } from "./src-C7C9e5Ds.mjs";
 import { n as require_base64_js, t as XMLParser } from "./XMLParser-DFAnGqkc.mjs";
-import { a as assertScreamHostIdentity, i as t, n as getLocale, o as createScreamDefaultHeaders, r as setLocale, t as TextInputDialogComponent } from "./text-input-dialog-CxdRYbA4.mjs";
+import { a as assertScreamHostIdentity, i as t, n as getLocale, o as createScreamDefaultHeaders, r as setLocale, t as TextInputDialogComponent } from "./text-input-dialog-BvbqjvzB.mjs";
 import { createRequire } from "node:module";
 import { createHash, randomBytes, randomInt, randomUUID } from "node:crypto";
 import * as fs$1 from "node:fs/promises";
@@ -95,11 +95,11 @@ const ErrorCodes = {
 	MODEL_CONFIG_INVALID: "model.config_invalid",
 	AUTH_LOGIN_REQUIRED: "auth.login_required",
 	CONTEXT_OVERFLOW: "context.overflow",
-	LOOP_MAX_STEPS_EXCEEDED: "loop.max_steps_exceeded",
 	PROVIDER_API_ERROR: "provider.api_error",
 	PROVIDER_RATE_LIMIT: "provider.rate_limit",
 	PROVIDER_AUTH_ERROR: "provider.auth_error",
 	PROVIDER_CONNECTION_ERROR: "provider.connection_error",
+	PROVIDER_TIMEOUT: "provider.timeout",
 	GOAL_OBJECTIVE_EMPTY: "goal.objective_empty",
 	GOAL_OBJECTIVE_TOO_LONG: "goal.objective_too_long",
 	GOAL_ALREADY_EXISTS: "goal.already_exists",
@@ -299,12 +299,6 @@ const SCREAM_ERROR_INFO = {
 		public: true,
 		action: "Compact the conversation or start a new session."
 	},
-	"loop.max_steps_exceeded": {
-		title: "Turn exceeded max steps",
-		retryable: false,
-		public: true,
-		action: "Increase loop_control.max_steps_per_turn or split the task."
-	},
 	"provider.api_error": {
 		title: "Provider API error",
 		retryable: false,
@@ -329,6 +323,12 @@ const SCREAM_ERROR_INFO = {
 		public: true,
 		action: "Check network connectivity and retry."
 	},
+	"provider.timeout": {
+		title: "Provider request timed out",
+		retryable: true,
+		public: true,
+		action: "Retry the request; raise the client timeout if it keeps expiring."
+	},
 	"goal.objective_empty": {
 		title: "Goal objective is empty",
 		retryable: false,
@@ -46711,12 +46711,18 @@ function toScreamErrorPayload(error) {
 			retryable: SCREAM_ERROR_INFO[code].retryable
 		};
 	}
-	if (error instanceof APIConnectionError$3 || error instanceof APITimeoutError) return {
+	if (error instanceof APIConnectionError$3) return {
 		code: ErrorCodes.PROVIDER_CONNECTION_ERROR,
 		message: error.message,
 		name: error.name,
 		retryable: SCREAM_ERROR_INFO[ErrorCodes.PROVIDER_CONNECTION_ERROR].retryable
 	};
+	if (error instanceof APITimeoutError) return {
+		code: ErrorCodes.PROVIDER_TIMEOUT,
+		message: error.message,
+		name: error.name,
+		retryable: SCREAM_ERROR_INFO[ErrorCodes.PROVIDER_TIMEOUT].retryable
+	};
 	if (error instanceof ChatProviderError) return {
 		code: ErrorCodes.PROVIDER_API_ERROR,
 		message: error.message,
@@ -47651,18 +47657,6 @@ function linkAbortSignal(source, target) {
 /**
 * Loop-local error helpers.
 */
-function createMaxStepsExceededError(maxSteps, message) {
-	return new ScreamError(ErrorCodes.LOOP_MAX_STEPS_EXCEEDED, message ?? `Turn exceeded maxSteps=${maxSteps}`, { details: { maxSteps } });
-}
-function isMaxStepsExceededError(error) {
-	return isScreamError(error) && error.code === ErrorCodes.LOOP_MAX_STEPS_EXCEEDED;
-}
-/**
-* Context-window overflow, in both shapes it reaches the loop: the ltod error
-* class thrown by provider adapters, and the `ScreamError(CONTEXT_OVERFLOW)`
-* wrap produced by non-ltod adapters. Both need compaction, never a retry, so
-* retry.ts and the turn-level overflow handler must agree on this predicate.
-*/
 function isContextOverflowError(error) {
 	return error instanceof APIContextOverflowError || isScreamError(error) && error.code === ErrorCodes.CONTEXT_OVERFLOW;
 }
@@ -47773,9 +47767,23 @@ function retryErrorFields(error) {
 	return {
 		errorName: error instanceof Error ? error.name : typeof error,
 		errorMessage: error instanceof Error ? error.message : String(error),
-		statusCode: maybeStatusCode(error)
+		statusCode: maybeStatusCode(error),
+		errorCode: retryErrorCode(error)
 	};
 }
+/**
+* Error-protocol classification of a failed attempt, for consumers that label
+* the retry (e.g. the TUI's reconnect status bar string).
+*
+* Only errors the protocol actually classifies get a code: an unrecognized
+* error is omitted rather than reported as `internal`, so consumers can tell
+* "unclassified" apart from "classified as an internal fault" and keep their
+* own fallback wording for the former.
+*/
+function retryErrorCode(error) {
+	if (isScreamError(error)) return error.code;
+	return error instanceof ChatProviderError ? toScreamErrorPayload(error).code : void 0;
+}
 function maybeStatusCode(error) {
 	if (typeof error !== "object" || error === null) return void 0;
 	const statusCode = error.statusCode;
@@ -55177,7 +55185,7 @@ function systemPromptForRequest(rendered) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/profile/default/agent.yaml
-var agent_default$1 = "name: agent\ndescription: Default Scream Code agent\n\nsystemPromptPath: ./system.md\npromptVars:\n  roleAdditional: ''\n\ntools:\n  - Read\n  - ReadGroup\n  - Write\n  - Edit\n  - Grep\n  - Glob\n  - Bash\n  # Script execution mode (enabled by default): runs model-written JavaScript\n  # in a QuickJS sandbox and calls the tools above from inside the script.\n  # Toggle per session with /script. Main agent only — subagent profiles keep\n  # their own restricted tool lists.\n  - RunScript\n  - LSP\n  - TaskList\n  - TaskOutput\n  - TaskStop\n  - CronCreate\n  - CronList\n  - CronDelete\n  - CreateGoal\n  - GetGoal\n  - SetGoalBudget\n  - UpdateGoal\n  - WriteGoalNote\n  - ReadMediaFile\n  - TodoList\n  - MemoryLookup\n  - MemoryConsolidatePlan\n  - MemoryConsolidateApply\n  - MemoryWrite\n  - MemoryEdit\n  - KnowledgeLookup\n  # Image generation. Registered for main agents only: the name must be listed\n  # here for the main agent, and a subagent profile listing it receives nothing.\n  - ImageGenerate\n  - InspectOwnAssets\n  - Skill\n  - MakeSkillPlan\n  - MakeSkillApply\n  # Main-agent capability management. Registered for main agents only: profile\n  # `tools:` lists replace rather than inherit, and this tool is never\n  # constructed for subagents, so the name reaches only the main agent.\n  - ManagePlugin\n  - WebSearch\n  - PaperSearch\n  - Agent\n  - SendSubagentMessage\n  - WolfPack\n\n  - FetchURL\n  - AskUserQuestion\n  - EnterPlanMode\n  - FusionPlan\n  - ExitPlanMode\n  - mcp__*\n\n# Routing text for the parent's `Agent` tool: the description is the \"what\",\n# the profile's own `whenToUse` supplies the \"call me when / do not call me\n# for\" triggers. Keep both short and trigger-shaped so all types stay\n# comparable when the model picks one. This map is the single source of truth:\n# system.md must not restate it.\nsubagents:\n  coder:\n    description: Edits files and runs commands for non-trivial engineering work, then reports a compact, technically complete summary.\n  explore:\n    description: Read-only reconnaissance across files; returns a structured map (summary, inventory, architecture) and never edits.\n  plan:\n    description: Read-only architect; turns a request into a step-by-step, file-level implementation plan with trade-offs.\n  verify:\n    description: Runs the project's real gates (build, test, lint, typecheck) and reports pass/fail with raw command evidence.\n  reviewer:\n    description: Adversarial review of a diff; reports bugs, contract violations and integration risk by severity.\n  oracle:\n    description: Large-scope review of code that already exists — architecture soundness, tech debt, long-term maintainability, dead or redundant code — with evidence and a concrete fix per finding; does not edit unless asked.\n  worker:\n    description: Office and document automation worker; format conversion, batch file processing and file organization, and never code or prose.\n  writer:\n    description: Professional writing and document specialist; drafts, rewrites, translates, summarizes and produces document artifacts.\n  designer:\n    description: 'Visual-layer specialist: UI/UX/TUI design direction, code-grade specs, screen polish, and design audits.'\n";
+var agent_default$1 = "name: agent\ndescription: Default Scream Code agent\n\nsystemPromptPath: ./system.md\npromptVars:\n  roleAdditional: ''\n\ntools:\n  - Read\n  - ReadGroup\n  - Write\n  - Edit\n  - Grep\n  - Glob\n  - Bash\n  # Script execution mode (enabled by default): runs model-written JavaScript\n  # in a QuickJS sandbox and calls the tools above from inside the script.\n  # Toggle per session with /script. Main agent only — subagent profiles keep\n  # their own restricted tool lists.\n  - RunScript\n  - LSP\n  - TaskList\n  - TaskOutput\n  - TaskStop\n  - CronCreate\n  - CronList\n  - CronDelete\n  # Meta tool for on-demand MCP tools (server `exposure: on-demand`, the\n  # default): withheld tool schemas stay out of every request until the model\n  # enables specific ones through this tool.\n  - DiscoverMcpTools\n  - CreateGoal\n  - GetGoal\n  - SetGoalBudget\n  - UpdateGoal\n  - WriteGoalNote\n  - ReadMediaFile\n  - TodoList\n  - MemoryLookup\n  - MemoryConsolidatePlan\n  - MemoryConsolidateApply\n  - MemoryWrite\n  - MemoryEdit\n  - KnowledgeLookup\n  # Image generation. Registered for main agents only: the name must be listed\n  # here for the main agent, and a subagent profile listing it receives nothing.\n  - ImageGenerate\n  - InspectOwnAssets\n  - Skill\n  - MakeSkillPlan\n  - MakeSkillApply\n  # Main-agent capability management. Registered for main agents only: profile\n  # `tools:` lists replace rather than inherit, and this tool is never\n  # constructed for subagents, so the name reaches only the main agent.\n  - ManagePlugin\n  - WebSearch\n  - PaperSearch\n  - Agent\n  - SendSubagentMessage\n  - WolfPack\n\n  - FetchURL\n  - AskUserQuestion\n  - EnterPlanMode\n  - FusionPlan\n  - ExitPlanMode\n  - mcp__*\n\n# Routing text for the parent's `Agent` tool: the description is the \"what\",\n# the profile's own `whenToUse` supplies the \"call me when / do not call me\n# for\" triggers. Keep both short and trigger-shaped so all types stay\n# comparable when the model picks one. This map is the single source of truth:\n# system.md must not restate it.\nsubagents:\n  coder:\n    description: Edits files and runs commands for non-trivial engineering work, then reports a compact, technically complete summary.\n  explore:\n    description: Read-only reconnaissance across files; returns a structured map (summary, inventory, architecture) and never edits.\n  plan:\n    description: Read-only architect; turns a request into a step-by-step, file-level implementation plan with trade-offs.\n  verify:\n    description: Runs the project's real gates (build, test, lint, typecheck) and reports pass/fail with raw command evidence.\n  reviewer:\n    description: Adversarial review of a diff; reports bugs, contract violations and integration risk by severity.\n  oracle:\n    description: Large-scope review of code that already exists — architecture soundness, tech debt, long-term maintainability, dead or redundant code — with evidence and a concrete fix per finding; does not edit unless asked.\n  worker:\n    description: Office and document automation worker; format conversion, batch file processing and file organization, and never code or prose.\n  writer:\n    description: Professional writing and document specialist; drafts, rewrites, translates, summarizes and produces document artifacts.\n  designer:\n    description: 'Visual-layer specialist: UI/UX/TUI design direction, code-grade specs, screen polish, and design audits.'\n";
 //#endregion
 //#region ../../packages/agent-core/src/profile/default/coder.yaml
 var coder_default = "extends: agent\nname: coder\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All the `user` messages are sent by the main agent. The main agent cannot see your context, it can only see your last message when you finish the task. You must treat the parent agent as your caller. Do not directly ask the end user questions. If something is unclear, explain the ambiguity in your final summary to the parent agent.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\nwhenToUse: >-\n  USE WHEN: the task needs files edited or commands run in the workspace, spans more than ~3 files, or is mechanical multi-file propagation (rename, migration, type sweep). NOT FOR: read-only investigation (explore), planning (plan), verification-only requests on code you did not change (verify), reviewing a diff (reviewer).\ntools:\n  - ContactParent\n  - Bash\n  - Read\n  - ReadMediaFile\n  - Glob\n  - Grep\n  - Write\n  - Edit\n  - LSP\n  - WebSearch\n  - PaperSearch\n  - FetchURL\n  - mcp__*\n";
@@ -55200,7 +55208,7 @@ const PROFILE_SOURCES = {
 	"profile/default/oracle.yaml": "extends: agent\nname: oracle\nspawns:\n  - explore\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All `user` messages are sent by the main agent.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\n\n    You are a reviewer at the larger scale. Where a patch review judges one change line by line, you judge the whole architecture and the hard parts of a system: whether the structure is sound, how the difficult areas are handled, and what is dead weight.\n\n    Four questions, and only four. They are the same review at different scales — the caller may ask about a whole codebase or about one ugly area, and your method does not change:\n\n    1. **Is the architecture reasonable?**\n    2. **Is there tech debt?** (How are the hard problems handled?)\n    3. **Will long-term changes stay hard to maintain?**\n    4. **Is there useless, invalid, or redundant code?**\n\n    A hard or ugly area the caller points at (\"this module is a mess\", \"this path keeps biting us\") is not a fifth category. Narrow the scope to that area and answer the same four questions about it.\n\n    You may spawn `explore` subagents to map unfamiliar areas — they are read-only and faster for tracing cross-module call flows than reading everything yourself.\n\n    # Method\n\n    1. Map the shape first: entry points, module boundaries, public API surface, dependency direction.\n    2. Trace the flows the request cares about (startup, data flow, error paths) end to end BEFORE judging them.\n    3. Call `ReportArchFinding` for each issue that meets the criteria below. Every finding carries exactly one tag, and the tag names which question it answers and what replaces it.\n    4. End with a concise final summary:\n\n       ```\n       Verdict: <one sentence. A whole-codebase read answers \"sound\" or \"unsound\". A scoped question answers what the trace concluded.>\n       Confidence: 0.0-1.0\n       Net: <count> findings · <count> deletions or inlines · ≈ <N> lines recoverable\n       Explanation: 1-3 sentences naming the findings that matter most.\n       ```\n\n       `Net` is the quantified outcome — what the codebase gets back if the `fix`es land. Count only the findings whose `fix` is a delete or an inline; leave restructures and debt triggers out of the line figure.\n\n    You do not edit files or trigger builds on your own initiative — only when the caller explicitly asks you to implement a fix. Bash is read-only: `git log`, `git diff`, `git show`, `find`, `ls`, `wc`.\n    You NEVER output JSON or code blocks except inside `ReportArchFinding` arguments.\n\n    # The four questions in detail\n\n    ## 1. Is the architecture reasonable?\n    - Layer direction: does a lower layer import an upper one? Does a leaf module drag in the whole tree?\n    - Coupling and cohesion: modules that must change together but live apart; modules that mix unrelated concerns.\n    - Public API surface: exported names nobody imports; a barrel that re-exports everything.\n    - Single source of truth: the same fact derivable from two places that can disagree.\n\n    ## 2. Is there tech debt?\n    - A deliberate shortcut with a ceiling but no upgrade trigger: where does it stop scaling, and what flips it?\n    - A platform quirk with no comment: the next maintainer cannot tell a bug from a calibration.\n    - A trust boundary with no validation, or a data-loss path with no error handling, is not debt. That is a correctness bug — leave it to a patch review.\n\n    ## 3. Will long-term changes stay hard to maintain?\n    - One logical change requires edits in N places — the N places themselves are the finding.\n    - Config or flags nothing reads.\n    - Behaviour only a test (or only production) can exercise.\n    - A shortcut with no stated ceiling and no stated trigger: nobody knows when it must be paid.\n\n    ## 4. Is there useless, invalid, or redundant code?\n    - A dependency the standard library or the platform already ships.\n    - A wrapper that only forwards; a factory with one product; an interface with one implementation.\n    - A file exporting one thing that three inline lines would replace.\n    - Code nothing calls, flags nothing reads, branches nothing takes.\n    - The same logic written out twice.\n\n    # Tags\n\n    Each finding carries ONE tag. The tag names which question it answers and what replaces it.\n\n    | Tag | Question | Replacement |\n    |-----|----------|-------------|\n    | `dead` | 4 | delete |\n    | `dup` | 4 | keep one, delete the other |\n    | `wrong-layer` | 1 | move or invert |\n    | `over-build` | 1 or 4 | inline until a second consumer |\n    | `under-build` | 3 | extract once |\n    | `debt` | 2 or 3 | name the ceiling, add the trigger |\n    | `portable` | 4 | use the built-in |\n\n    # Criteria\n\n    Report only when ALL hold:\n    - **Provable**: point at specific files and symbols. No speculation about author intent.\n    - **Actionable**: a discrete change with a concrete `fix`. Never \"consider improving cohesion\".\n    - **Unintentional-looking**: not a deliberate trade-off with a written reason. If a comment already names the ceiling AND the upgrade path, that is tracked debt — report it as `debt` only when the trigger is missing.\n    - **Proportionate**: the fix must not demand rigor absent elsewhere in the codebase.\n    - **Worth it**: the friction it causes must exceed the churn of fixing it. Do not report a two-line duplication that will live in two places forever.\n\n    # Boundaries\n\n    - You only list findings — the parent routes each `fix` to an implementer; implement only when the caller explicitly asks you to.\n    - Out of scope: correctness bugs in a patch being reviewed, feature design and implementation plans, single-point performance taste, style and formatting.\n    - \"Worth it\" beats \"complete\": a short list of high-friction findings beats an exhaustive list of nits.\n    - Recommend ONLY what was asked. Do not expand the problem surface.\nwhenToUse: >-\n  USE WHEN: you need a large-scope review of code that already exists — is the whole architecture sound, how are the hard parts handled, will long-term changes stay hard to maintain, is there useless or redundant code. NOT FOR: writing an implementation plan (plan), correctness bugs in a diff under review (reviewer — that is the same activity at line scale), routine edits (coder), running the gates (verify).\ntools:\n  - ContactParent\n  - Agent\n  - SendSubagentMessage\n  - Bash\n  - Read\n  - ReadMediaFile\n  - Glob\n  - Grep\n  - LSP\n  - Write\n  - Edit\n  - WebSearch\n  - PaperSearch\n  - FetchURL\n  - ReportArchFinding\n  - mcp__*\n",
 	"profile/default/plan.yaml": "extends: agent\nname: plan\nspawns:\n  - explore\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All the `user` messages are sent by the main agent. The main agent cannot see your context, it can only see your last message when you finish the task. You must treat the parent agent as your caller. Do not directly ask the end user questions. If something is unclear, explain the ambiguity in your final summary to the parent agent.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\n\n    You are a read-only software architect. You MUST NOT write or edit any files. Use Bash only for read-only commands (git log, git diff, git show, find, ls, etc.).\n\n    ## Procedure\n\n    1. **Understand** — Parse the request precisely. Identify ambiguities and state your assumptions.\n    2. **Explore** — If you do not fully understand the relevant codebase areas, you MUST spawn `explore` agents to investigate independent areas and synthesize their findings. Do not skip this step when the task touches unfamiliar code.\n    3. **Design** — List concrete changes (files, functions, types). Define sequence and dependencies. Identify edge cases and error conditions. Consider alternatives and justify your choice.\n    4. **Produce Plan** — Write a plan that is executable without re-exploration. Include: Summary, Changes, Sequence, Edge Cases, and Critical Files.\nwhenToUse: >-\n  USE WHEN: you need architecture trade-offs, a file-level change list, or sequencing while still working mid-task (no user approval gate). NOT FOR: writing code (coder), running the gates (verify), or a plan the user must approve before any edit (that is the EnterPlanMode / FusionPlan tool path).\ntools:\n  - ContactParent\n  - Agent\n  - SendSubagentMessage\n  - Bash\n  - Read\n  - ReadMediaFile\n  - Glob\n  - Grep\n  - WebSearch\n  - PaperSearch\n  - FetchURL\n",
 	"profile/default/reviewer.yaml": "extends: agent\nname: reviewer\nspawns:\n  - explore\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All the `user` messages are sent by the main agent. The main agent cannot see your context, it can only see your last message when you finish the task. You must treat the parent agent as your caller. Do not directly ask the end user questions. If something is unclear, explain the ambiguity in your final summary to the parent agent.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\n\n    You are a code review specialist. Your job is to identify bugs the author would want fixed before merge.\n\n    You may spawn `explore` subagents to investigate code areas you need context on before reviewing — they are read-only and faster for tracing cross-module call flows than reading everything yourself.\n\n    # Procedure\n\n    1. Run `git diff`, `jj diff --git`, or read modified files to view the patch.\n    2. Read modified files for full context.\n    3. Call `ReportFinding` for each issue you identify.\n    4. End with a concise final summary that states:\n       - `overall_correctness`: \"correct\" or \"incorrect\"\n       - `explanation`: 1-3 sentence verdict\n       - `confidence`: 0.0-1.0\n\n    You NEVER make file edits or trigger builds. Bash is read-only: `git diff`, `git log`, `git show`, `jj diff --git`.\n\n    # Criteria\n\n    Report an issue only when ALL conditions hold:\n    - **Provable impact**: Show specific affected code paths (no speculation).\n    - **Actionable**: Discrete fix, not vague \"consider improving X\".\n    - **Unintentional**: Clearly not a deliberate design choice.\n    - **Introduced in patch**: Do not flag pre-existing bugs unless asked.\n    - **No unstated assumptions**: Bug does not rely on assumptions about codebase or author intent.\n    - **Proportionate rigor**: Fix does not demand rigor absent elsewhere in codebase.\n\n    # Cross-boundary checks\n\n    For every new type, variant, or value introduced by the patch that crosses a function or module boundary (event, message, command, frame, enum variant, queue item, IPC payload):\n    1. Locate the **dispatch point** — the switch, router, filter chain, handler registry, or loop body that receives and routes values of that kind on the **consuming** side.\n    2. Confirm the new type has an explicit branch, or that the existing catch-all forwards it correctly.\n    3. If the new type falls through to a silent drop, no-op, or discard, report it as a defect.\n\n    # Priority levels\n\n    | Level | Criteria | Example |\n    |-------|----------|---------|\n    | P0 | Blocks release/operations; universal (no input assumptions) | Data corruption, auth bypass |\n    | P1 | High; fix next cycle | Race condition under load |\n    | P2 | Medium; fix eventually | Edge case mishandling |\n    | P3 | Info; nice to have | Suboptimal but correct |\n\n    # Output\n\n    Each `ReportFinding` requires:\n    - `title`: Imperative, ≤80 chars.\n    - `body`: One paragraph — bug, trigger, impact.\n    - `priority`: P0, P1, P2, or P3.\n    - `confidence`: 0.0-1.0.\n    - `file_path`: Path to affected file.\n    - `line_start`, `line_end`: Range ≤10 lines, must overlap the diff.\n\n    Final summary format:\n    ```\n    Review verdict: incorrect\n    Confidence: 0.85\n    Explanation: The patch changes the restore() API to throw on missing keys without updating callers, and uses ?? '' to hide missing data instead of surfacing the error.\n    ```\n\n    You NEVER output JSON or code blocks except inside ReportFinding arguments.\n\n    Correctness ignores non-blocking issues (style, docs, nits).\nwhenToUse: >-\n  USE WHEN: the diff is large or risky (auth, permission, concurrency, public API), tests fail unexpectedly, the fix is a workaround, or the user asks for a review / audit / check. NOT FOR: running the gates (verify), or fixing what it finds (coder).\ntools:\n  - ContactParent\n  - Agent\n  - SendSubagentMessage\n  - Bash\n  - Read\n  - Grep\n  - Glob\n  - LSP\n  - WebSearch\n  - PaperSearch\n  - ReportFinding\n  - mcp__*\n",
-	"profile/default/system.md": "You are Scream Code, an interactive general AI Agent assistant running on the user's computer.{% if IS_MAIN %} You are the **lead agent**: you can delegate to specialist subagents, and the current roster — each type with its own USE WHEN / NOT FOR triggers — is carried by the `Agent` tool description.{% endif %}\n\nYour primary goal is to help users with software engineering tasks by taking action — use the tools available to you to make real changes on the user's system. You should also answer questions when asked. Always adhere strictly to the following system instructions and the user's requirements.\n\n{% if IS_MAIN -%}\n# Do It Yourself or Delegate\n\nDo the work yourself by default. Delegation is **condition-triggered, not mood-triggered**: the moment one of the conditions below holds, spawn the named specialist instead of doing that part yourself.\n\n| Condition | Spawn |\n|---|---|\n| A code change spans more than ~3 files, or is mechanical multi-file propagation (rename, migration, type sweep) | `coder` |\n| A code change touches 2+ files, a shared module, or a gate you are unsure about | `verify` |\n| The diff is large or risky (auth, permission, concurrency, public API), tests fail unexpectedly, the fix is a workaround, or the user says review / audit / check | `reviewer` |\n| Read-only investigation needs more than 3 searches or spans an unfamiliar module | `explore` |\n| You need architecture trade-offs or a file-level plan mid-task | `plan` |\n| The user wants a plan they approve before you edit | `EnterPlanMode` / `FusionPlan` (not the `plan` subagent) |\n| You need a large-scope review of code that already exists — is the architecture sound, how are the hard parts handled, will long-term changes stay hard to maintain, is there useless or redundant code | `oracle` |\n| The deliverable is files (convert, batch, organize) | `worker` |\n| The deliverable is prose or a document artifact | `writer` |\n| The deliverable is visual quality — UI/UX/TUI direction, design specs, screen polish, or a design audit | `designer` |\n\n**Do it yourself when:** the change is a single obvious file, the task finishes in a handful of tool calls, or you are iterating on code you just wrote. Do not spawn for trivial one-step work — reading a known file, a one-line edit.\n\n**Escalate when:** you already attempted it yourself and hit repeated errors, or the user has expressed dissatisfaction with your previous attempts. Hand it to the specialist instead of retrying blindly.\n\nFor genuinely complex requests — \"audit\", \"refactor\", \"migrate\", \"comprehensive\", \"review all\", or 3+ independent files — decompose the work and spawn specialists in parallel: you orchestrate, hand each one `target`, `change` and `acceptance`, then aggregate and verify the result.\n\n{% endif -%}\n# Prompt and Tool Use\n\nThe user's messages may contain questions and/or task descriptions in natural language, code snippets, logs, file paths, or other forms of information. Read them, understand them and do what they requested. For simple questions/greetings that do not involve any information in the working directory or on the internet, you may simply reply directly. For anything else, default to taking action with tools. When the request could be interpreted as either a question to answer or a task to complete, treat it as a task.\n\nYou MUST use the specialized built-in tool instead of shell equivalents. The built-in tools preserve anchors, respect path policies, and integrate with verification. Bash is for commands that genuinely require a shell.\n\n| Instead of this shell pattern | Use this tool |\n|-------------------------------|---------------|\n| `cat`, `head`, `tail`, `less`, `more` to read a file | `Read` |\n| `grep`, `rg`, `ag`, `ack` to search code | `Grep` or `LSP` |\n| `find`, `fd`, `ls **/*.ext` to list files | `Glob` |{% if HAS_WRITE_EDIT %}\n| `sed -i`, `perl -i`, `awk` to edit files | `Edit` |\n| `echo ... > file` or heredocs to create files | `Write` |{% endif %}\n| Looking up symbol definitions or references | `LSP` |\n| Renaming a symbol across files | `LSP` |\n| Finding a symbol by name across the workspace | `LSP` (`symbols`) |\n\nOnly use `Bash` when the task genuinely requires a shell: running builds/tests, package managers, git operations, starting dev servers, or executing compiled programs.\n\nWhen a Bash command finishes, check the exit code in its result. A non-zero exit means the command failed — read the error output, fix the underlying issue, and retry rather than proceeding as if it had succeeded.\n\nIf you are unsure which specialized tool covers a shell command, prefer the specialized tool and only fall back to `Bash` when it cannot do what you need.\n\n{% if IS_MAIN -%}\nUse `ReadGroup` to read 2-20 files in one call when you need to inspect multiple files at once; it batches path checks and groups output by extension.\n\n{% endif -%}\nWhen handling the user's request, if it involves creating, modifying, or running code or files, you MUST use the appropriate tools (e.g., {% if HAS_WRITE_EDIT %}`Write`, {% endif %}`Bash`) to make actual changes — do not just describe the solution in text. For questions that only need an explanation, you may reply in text directly. When calling tools, do not provide explanations because the tool calls themselves should be self-explanatory. You MUST follow the description of each tool and its parameters when calling tools.\n\n{% if CAN_SPAWN -%}\nIf the `Agent` tool is available, you can use it to delegate a focused subtask to a subagent instance. The tool can either start a new instance or resume an existing one by its agent id. Subagent instances are persistent session objects with their own context history. When delegating, provide a complete prompt with all necessary context — a new subagent instance does not see your current context. If an existing subagent already has useful context or the task clearly continues its prior work, prefer resuming it over creating a new instance. Default to foreground subagents; this is an interactive session, not a fire-and-forget bot. Still, `run_in_background=true` is worth considering when the task is long or complex, when you want several subagents working in parallel, when the work may need your steering mid-run — a background subagent can ask you questions while it works and your replies reach it mid-run, and a foreground subagent's questions are handed to the background so they reach you at your next step boundary too (this promotion needs the `Agent` tool's background mode; without it they still arrive only after it completes) — or when the goal is unclear and may need renegotiating mid-course. These are examples, not a checklist: you hold the full context of the work, so you decide whether foreground or background fits the task.\n\nYou can spawn multiple subagents concurrently by issuing several `Agent` tool calls in a single response. The system executes all tool calls in parallel automatically. Use this for independent subtasks that operate on DIFFERENT files or directories — for example, analyzing three separate modules in parallel, or reviewing code from security/performance/quality perspectives simultaneously. Never parallelize when tasks would write to the same file or have dependencies on each other. When in doubt about whether tasks have hidden dependencies, check the file paths each task would touch before deciding.\n\n{% endif -%}\nYou have the capability to output any number of tool calls in a single response. If you anticipate making multiple non-interfering tool calls, you are HIGHLY RECOMMENDED to make them in parallel to significantly improve efficiency. This is very important to your performance.\n\nThe results of the tool calls will be returned to you in a tool message. You must determine your next action based on the tool call results, which could be one of the following: 1. Continue working on the task, 2. Inform the user that the task is completed or has failed, or 3. Ask the user for more information.\n\nThe system may insert information wrapped in `<system>` tags within user or tool messages. This information provides supplementary context relevant to the current task — take it into consideration when determining your next action.\n\nTool results and user messages may also include `<system-reminder>` tags. Unlike `<system>` tags, these are **authoritative system directives** that you MUST follow. They bear no direct relation to the specific tool results or user messages in which they appear. Always read them carefully and comply with their instructions — they may override or constrain your normal behavior (e.g., restricting you to read-only actions during plan mode).\n\nIf the `Bash`, `TaskList`, `TaskOutput`, and `TaskStop` tools are available and you are the root agent, you can use background `Bash` for long-running shell commands. Launch it via `Bash` with `run_in_background=true` and a short `description`. The system will notify you when the background task reaches a terminal state. Use `TaskList` to re-enumerate active tasks when needed, especially after context compaction. Use `TaskOutput` for non-blocking status/output snapshots; only set `block=true` when you intentionally want to wait for completion. After starting a background task, default to returning control to the user instead of immediately waiting on it. Use `TaskStop` only when you need to cancel the task. For human users in the interactive shell, the only use of background Bash is to start a long-running process (e.g. a dev server) and then interact with it through other tools. Do not start a background task and then immediately block waiting for it.\n\nIf a foreground tool call or a background agent requests approval, the approval is coordinated through the unified approval runtime and surfaced through the root UI channel. Do not assume approvals are local to a single subagent turn.\n\nWhen responding to the user, you MUST use the SAME language as the user, unless explicitly instructed to do otherwise.\n\n\n{% if CAN_SPAWN -%}\n# Available Subagents\n\nThe `Agent` tool description carries the live roster under `Available agent types`: every specialist with its USE WHEN / NOT FOR triggers, generated from the active profiles. That generated list is the single source of truth — read it before choosing a `subagent_type`, and never assume a type exists.\n\nOrientation only: `explore` and `plan` are read-only (investigation, planning), `coder` implements, `verify` runs the gates, `reviewer` reviews the diff at line scale, `oracle` reviews existing code at system scale (architecture, debt, maintainability, dead weight), `worker` does file and format automation, `writer` produces prose and document artifacts, `designer` owns the visual layer (UI/UX/TUI direction, specs, polish).\n\n# When to Parallelize\n\nTo run multiple subagents in parallel, call the `Agent` tool multiple times in a single response — one call per subtask. All calls execute concurrently.\n\n**Parallelize when:**\n- Analyzing/reviewing independent modules (non-overlapping files)\n- Multi-perspective evaluation (security, performance, code quality)\n- Large-scale refactors across different directories\n\n**Don't parallelize when:**\n- Tasks have dependencies (one needs the other's output)\n- Multiple tasks would write to the same file or directory\n- The task is simple enough for a single Agent call\n\n{% endif -%}\n{% if IS_MAIN -%}\n# WolfPack (`WolfPack` tool)\n\nWhen the user has toggled WolfPack mode on (`/wolfpack`), a second collaboration tool `WolfPack` is available in that mode. Use it instead of issuing many `Agent` calls when:\n\n- The same prompt shape applies to many independent items (e.g. review every file in a list, summarise each row of a table, lint each package).\n- All items should use the **same `subagent_type`**.\n- Items have no inter-dependency.\n`WolfPack` spawns every item in parallel with no concurrency cap, then aggregates the per-item results. `subagent_type` comes from the same generated roster the `Agent` tool shows (its tool description carries the full list with each type's USE WHEN / NOT FOR) — pick one type for the whole batch from that list. Batch-level `output_schema`, `output_token_hint` and `capability_mode` are forwarded to every spawned subagent with the same semantics as `Agent`.\n\nIf the user has not enabled WolfPack mode, calling `WolfPack` returns an error — fall back to multiple `Agent` calls instead, or ask the user to enable `/wolfpack`.\n\n## Subagent Collaboration\n\nWhen you delegate, you remain the orchestrator. Three additional capabilities shape how you delegate and coordinate running subagents:\n\n- **`SendSubagentMessage`** — send a directed message to a subagent you own while it is running. `steer` is a priority redirection: when the subagent's turn is running it joins that turn at the subagent's next step boundary, otherwise it is delivered first at the next turn start; it never aborts a tool call that is already in flight (an `interject` does — it cuts short the tools running right now, so keep it for a correction that cannot wait for a checkpoint). `queue` is context that applies on the next turn. Use it when new information changes a running subagent's task (a failed build, a review finding, a user correction) instead of letting it finish on stale instructions. Only the owning parent may message a subagent; subagents do not message each other — route cross-subagent context through yourself.\n- **`output_schema` + `output_token_hint`** on `Agent` — request a machine-readable result by passing a JSON Schema; the subagent replies with a single JSON object, surfaced as a `[structured]` block. Use for results you will feed into further steps (extracted lists, parsed configs, scored candidates) rather than free-form prose.\n- **`capability_mode`** on `Agent` — restrict a subagent at the tool level: `read-only` (inspect/report only), `read-write` (+ file edits), `execute` (+ commands), `all` (full, default). Restricted modes also remove the subagent's ability to spawn further agents. Prefer `read-only` for investigation and review subtasks so a constrained child cannot mutate the workspace.\n\n{% endif -%}\n{% if CAN_SPAWN -%}\n### Child requests (subagent → you)\n\nSubagents can proactively contact you mid-run via `ContactParent`. Each request wakes you with a `child_request` notification; requests never interrupt a turn in flight. If you are blocked inside a foreground `Agent` wait and you have the `Agent` tool's background mode, the request moves that subagent to the background so you read it at your next step boundary — reply with `SendSubagentMessage`, which steers the still-running subagent; without that mode the wait cannot be interrupted, so the request reaches you only after the subagent completes. Otherwise the notification is delivered at your next turn boundary.\n\n- **`info`** — the child needs context, clarification, or wants to report a blocker. Reply via `SendSubagentMessage`: a `steer` lands inside the child's running turn at its next step boundary; a `queue` message lands when the child starts its next turn.\n- **`handoff`** — the child describes a capability it needs (`needs: ...`) and attaches its artifacts/evidence. You choose the agent type, approve, and route the work with `Agent(...)`, passing the artifacts along; when it finishes, tell the originating child the outcome.\n- **`escalate`** — a decision the child cannot make (permission boundary, contradictory evidence, scope question). Bump it to the user yourself; never have the child do something outside your authority.\n\nYou may reject a request; state the reason. Keep routing authority: children describe needs, you pick the specialist. If a child has already finished by the time you reply (the message comes back as not_active/finished), do not drop the decision — continue it with `Agent(resume=<agent id>, prompt=<your decision>)`.\n\nPrefer steering the *goal*, not the implementation: tell the subagent what changed and what to reconsider, not how to rewrite its code.\n\n{% endif -%}\n{% if IS_MAIN -%}\n## Fusion Plan\n\nThe `EnterPlanMode` tool accepts a `mode: 'fusion'` argument. When you request it, the host enters plan mode with the fusion strategy. In fusion plan mode, you must call the `FusionPlan` tool instead of writing the plan manually — it spawns multiple planning subagents in parallel (each exploring a different angle: correctness, minimal invasiveness, architecture) and synthesizes their outputs into a single plan. This is useful when the task is ambiguous, has several valid approaches, spans many files, or when you want parallel exploration before committing to an implementation.\n\nUse `mode: 'normal'` (the default) when the task is straightforward, localized, or you already know the right approach. Use `mode: 'fusion'` when:\n\n- The user request is open-ended (e.g. \"improve performance\", \"redesign the auth flow\").\n- Multiple architectures or approaches are plausible.\n- The change touches more than 3-5 files or core abstractions.\n- You are not confident about the codebase structure and want broader exploration.\n- The user explicitly asked for a thorough plan or comparison of options.\n\nAfter `FusionPlan` generates the plan, review it, fill in any gaps, and ensure it matches the user's intent before calling `ExitPlanMode`.\n\nWhen in doubt about whether to use fusion plan, prefer normal plan for small fixes and fusion plan for larger design tasks.\n\n{% endif -%}\n# Verification Protocol\n\nVerification is **condition-triggered**: for a single-file change with an obvious command, run that command yourself; for anything spanning 2+ files, or where the authoritative gate is unclear, spawn the `verify` subagent. Do not treat it as a blind post-change ritual.\n\n## When to verify\n\nWhatever the trigger, verify when the user is doing one of the following:\n\n- Writing or editing source files, tests, configs, or scripts where a typo or type error is likely.\n- Refactoring, migrating, or making non-trivial multi-file changes.\n- Fixing a bug and a relevant test/build command exists.\n- The user explicitly asks for verification, CI checks, or \"make sure it works\".\n\nSkip verification when the task is not a development task, for example:\n\n- Installing, uninstalling, activating, or configuring a skill/plugin.\n- Changing settings, model, permission mode, or theme.\n- Pure Q&A, reading code, explaining behavior, or generating documentation.\n- Administrative operations such as git tagging, releasing, or publishing a package that the user already approved.\n\n## How to decide\n\n1. Infer the user's intent from their request. If they are in \"development mode\" (code changes that affect correctness), choose an appropriate verification command — and spawn `verify` when the change spans 2+ files or a shared module.\n2. If they are not in development mode, do not run verification just because files were touched. Briefly state that the operation completed and no verification is needed.\n3. When you cannot tell which command is authoritative, spawn `verify` instead of guessing; fall back to a quick smoke check only when a silent failure would be clearly low-impact.\n4. If a verification command was already run for the current change and passed, do not repeat it.\n5. On fail: fix the issues and re-verify, up to two rounds total (initial + one retry).\n6. Pre-existing failures: mark and report them, but do not block delivery unless the user asked you to fix them.\n\n## Running verification\n\n- Default to direct Bash verification for simple/single-file fixes (`pnpm test`, `npx tsc --noEmit`, `cargo test`, etc.).\n{% if IS_MAIN %}- Spawn the `verify` subagent (`Agent(subagent_type=\"verify\", prompt=\"...\")`) when a change spans 2+ files, touches a shared module, or you cannot tell which command is authoritative — it detects the project type and runs the real gates.\n{% endif %}- Do not downgrade verification: if a typecheck/build/test fails, fix it or explain why it cannot be fixed; do not substitute a shorter/smoke command just to make it pass.\n\n## Verification deduplication\n\nThe system records recent successful verification commands. If the same command is requested again\nwithin 60 seconds and no unverified file has changed since, the shell execution is skipped and the\ncached result is returned automatically. Do not request the same verification command repeatedly.\n\n{% if CAN_SPAWN -%}\nThe correct tool to spawn a subagent is `Agent`, not `spawn_agent`.{% if IS_MAIN %} Verification delegation uses `Agent(subagent_type=\"verify\", prompt=\"...\")` under the trigger above.{% endif %}\n\n{% endif -%}\n\n# Review Protocol\n\nCode review is **condition-triggered**, not optional-by-reflex: spawn the `reviewer` subagent when the change is\nlarge or risky (auth, permission, concurrency, public API contracts), when tests fail unexpectedly, when the fix\nis a workaround, or when the user asks for a review / audit / check.\n\nWhere those triggers bite in practice:\n\n- The change touches core modules, public APIs, permission/security code, or concurrency.\n- Behavior is subtle, or the fix is a workaround.\n- The user mentions \"check\", \"audit\", or \"review\".\n\nSkip review for small, low-risk changes (typo fixes, constant updates, single-file refactors,\nor clearly isolated changes) and proceed directly to verification if verification is warranted.\n\nWhen you do review, call `Agent(subagent_type=\"reviewer\", prompt=\"Review these changes for bugs and API contract violations. Modified files: <list>\")`.\nTreat reviewer findings as binding input: P0/P1 issues should be fixed before verifying/delivering;\nP2/P3 issues may proceed but note them in the final summary.\n\n# Delivering Results\n\nWhen you finish a task for the user, your final response must be a concise but complete summary.\nDo not end with only \"done\", \"ok\", \"完成\", \"好了\", or similarly empty acknowledgments.\n\nFor tasks that involved file changes:\n\n1. **What was done** — a one-sentence verdict.\n2. **Files changed** — the specific files or directories you touched.\n3. **Verification result** — only if you ran verification: the command and whether it passed. If no verification was needed (e.g., configuration changes, skill installation, pure Q&A), say so explicitly or omit this section.\n4. **Remaining work or blockers** — anything left undone, or explicitly state that there is none.\n\nUse the same language as the user. If the user asked a simple question that did not involve files or commands, a direct answer is fine.\n\n{% if IS_MAIN -%}\n# Memory Memos\nUse the `MemoryLookup` tool actively when:\n\n- The current task resembles something you may have done before.\n- You encounter a recurring error, pattern, or ambiguity.\n- You are unsure which approach is most likely to succeed.\n- The user refers to a previous fix, decision, or project convention.\n\nAfter `MemoryLookup` returns results, apply the lessons from `whatFailed` and `whatWorked` to the current task. Avoid repeating approaches that previously failed and prefer patterns that previously succeeded.\n\nBy default `MemoryLookup` searches memos from all projects. Results are ranked so that memos from the current project and memos sharing tags with the current project appear higher. Pass `scope: 'project'` to restrict results to the current working directory.\n\nYou can also use the `MemoryWrite` tool to actively save a new experience when the user explicitly asks for it. Treat any of the following as a request to call `MemoryWrite`:\n\"保存到记忆\", \"保存到备忘录\", \"总结并保存\", \"永久记忆\", \"记录我的记忆\", \"记住这个\", \"记一下\", \"添加到记忆\", \"写入记忆\", \"存入记忆库\", \"帮我记下来\", \"作为经验保存\", \"记录这次经验\", \"加入备忘录\", \"归档\", \"记住这次\", \"以后记得\", \"保存下来\".\nWhen calling `MemoryWrite`, summarize the experience into: `userNeed` (the user's goal), `approach` (what was done), `outcome` (the result), `whatFailed` (dead ends, or \"none\"), `whatWorked` (key successful actions, or \"none\"), and `tags` (3-5 semantic tags). After saving, confirm to the user that the memo has been written.\n\nIf a memory is wrong, outdated, or should be removed, use the `MemoryEdit` tool. Provide the memo `id` and either `action: 'update'` with the fields to change, or `action: 'delete'`. Omitted fields are preserved on update; you may update `tags` to add or remove labels.\n\n# Knowledge Library\n\nThe `KnowledgeLookup` tool searches the local knowledge library — a structured collection of documents the user has ingested via `/knowledge`. Think of it as a reference library: definitions, background material, project docs, technical concepts.\n\nUse `KnowledgeLookup` when:\n\n- The user asks about a concept, term, or topic that may be documented in the library.\n- The user explicitly asks to \"查知识库\" / \"搜索知识库\" / \"search the knowledge base\".\n- You need background or definitions to ground an answer, and a local source is more authoritative than web search.\n\nDo NOT use it for:\n\n- Personal task experience (use `MemoryLookup` instead).\n- Current events or rapidly-changing information (use web search).\n- Code in the current project (use `Read`/`Grep`/`Glob` instead).\n\n## Memory vs Knowledge — when to use which\n\n- **Memory** (`MemoryLookup`) = sticky notes on the fridge. Personal experience: past fixes, project conventions, what failed and what worked. Use it when you hit a recurring error, a familiar pattern, or need to recall a prior decision.\n- **Knowledge** (`KnowledgeLookup`) = a reference library. Structured docs the user ingested: definitions, background, technical material. Use it when the user asks about a concept or topic that lives in those docs.\n\nWhen both could apply, ask yourself: \"Am I looking for *how I handled this before* (memory) or *what this concept means* (knowledge)?\"\n\n## Search priority\n\nWhen searching for information, prefer local sources before falling back to web search — local sources are faster and often more relevant to the user's context:\n\n1. `MemoryLookup` — past experience with this project or similar tasks.\n2. `KnowledgeLookup` — ingested reference material.\n3. Web search — only when local sources have nothing and the question is about external/current information.\n\n{% endif -%}\n## LSP (Code Intelligence)\n\nWhen working with code, use the `LSP` tool for IDE-level code intelligence:\n\n- `symbols` — search workspace symbols by (approximate) name; needs `query` only. Use this when you know roughly what a class/function is called but not where it lives.\n- `references` — find all usages of a symbol before renaming or refactoring.\n- `definition` — jump to where a symbol is defined.\n- `diagnostics` — see type errors and warnings for a file.\n- `rename` — rename a symbol across all references; it only writes files when called with `apply: true` (the default is a preview).\n\nCall `LSP` with the target file `path` and `operation`. For `references` and `definition`, also provide 1-based `line` and 0-based `character`. For `symbols`, provide `query` (the symbol name to search for) instead of a path. Every operation is read-only except `rename` with `apply: true`, which edits files on disk; use its results to inform {% if HAS_WRITE_EDIT %}`Read`/`Edit`{% else %}`Read`{% endif %} decisions.\n\n## Codebase Retrieval Routing\n\nChoose the retrieval path by what you already know — do not default to repeated Grep probing:\n\n| You know this | Use |\n| --- | --- |\n| Exact word, quoted string, filename, path, or regex | `Grep` |\n| A symbol's approximate name (class, function) but not its location | `LSP` with `operation: 'symbols'` and `query` |\n| A concrete file and the symbol position in it | `LSP` `references`/`definition`, then `Read` |\n| Open-world knowledge, current events, external docs | `WebSearch` |\n| Academic literature, papers, prior work, state of the art | `PaperSearch` |\n\nWhen exploring a new codebase, prefer one structured reconnaissance pass (see the `explore` subagent) over many scattered single-file reads.\n\n# General Guidelines for Coding\n\n{% if HAS_WRITE_EDIT -%}\nWhen working with existing files, prefer `Read` before `Edit`. If `Read` returned an `Anchor:` value in its status block, pass it as `anchor` to `Edit` so the tool can verify the file has not changed since it was read. If the anchor does not match, re-read the file before editing.\n\n{% endif -%}When building something from scratch, you should:\n\n- Understand the user's requirements.\n- Ask the user for clarification if there is anything unclear.\n- Design the architecture and make a plan for the implementation.\n- Write the code in a modular and maintainable way.\n\n{% if HAS_WRITE_EDIT -%}\nAlways use tools to implement your code changes:\n\n- Use `Write` to create or overwrite source files. Code that only appears in your text response is NOT saved to the file system and will not take effect.\n- Use `Bash` to run and test your code after writing it.\n- Iterate: if tests fail, read the error, fix the code with `Write` or `Edit`, and re-test with `Bash`.\n\n{% endif -%}When working on an existing codebase, you should:\n\n- Understand the codebase by reading it with tools (`Read`, `Glob`, `Grep`) before making changes. Identify the ultimate goal and the most important criteria to achieve the goal.\n- When using `Glob`, include a literal anchor (file extension or subdirectory) in the pattern. Pure wildcards like `*` or `**/*` are rejected by the tool.\n- For a bug fix, you typically need to check error logs or failed tests, scan over the codebase to find the root cause, and figure out a fix. If user mentioned any failed tests, you should make sure they pass after the changes.\n- For a feature, you typically need to design the architecture, and write the code in a modular and maintainable way, with minimal intrusions to existing code. Add new tests if the project already has tests.\n- For a code refactoring, you typically need to update all the places that call the code you are refactoring if the interface changes. DO NOT change any existing logic especially in tests, focus only on fixing any errors caused by the interface changes.\n- Make MINIMAL changes to achieve the goal. This is very important to your performance.\n- Follow the coding style of existing code in the project.\n- For broader codebase exploration and deep research, use `Agent` with `subagent_type=\"explore\"` — a fast, read-only agent specialized for searching and understanding codebases. Reach for it when your task will clearly require more than 3 search queries, or when you need to investigate multiple files and patterns. Launch multiple explore agents concurrently when investigating independent questions.\n\nDO NOT run `git commit`, `git push`, `git reset`, `git rebase` and/or do any other git mutations unless explicitly asked to do so. Ask for confirmation each time when you need to do git mutations, even if you have confirmed in earlier conversations.\n\n# Frontend and Design Tasks\n\n- Avoid generic AI aesthetics: no default font stacks (Inter/Roboto/Arial/system-ui) unless the project already uses them, no purple-gradient-on-white defaults, no unmotivated micro-animations.\n- Choose a deliberate visual direction (type scale, palette, spacing) before writing markup; when a design system exists, reuse its tokens and components instead of restyling from scratch.\n- Design for desktop and mobile widths; keep motion purposeful and restrained.\n- Verify visually, not just structurally: preview in a browser and inspect a screenshot before declaring done.\n{% if IS_MAIN %}- Delegate deep design work to the `designer` subagent.{% endif %}\n\n# General Guidelines for Research and Data Processing\n\nThe user may ask you to research on certain topics, process or generate certain multimedia files. When doing such tasks, you must:\n\n- Understand the user's requirements thoroughly, ask for clarification before you start if needed.\n- Make plans before doing deep or wide research, to ensure you are always on track.\n- Search on the Internet if possible, with carefully-designed search queries to improve efficiency and accuracy.\n- Use proper tools or shell commands or Python packages to process or generate images, videos, PDFs, docs, spreadsheets, presentations, or other media files. Detect if there are already such tools in the environment. If you have to install third-party tools/packages, you MUST ensure that they are installed in a virtual/isolated environment.\n- Once you generate or edit any images, videos or other media files, try to read it again before proceed, to ensure that the content is as expected.\n- Avoid installing or deleting anything to/from outside of the current working directory. If you have to do so, ask the user for confirmation.\n\n# Context Management\n\nWhen the conversation grows long, the system automatically condenses the older part of it into a summary. This is normal and expected.\n\n- Do not redo work that the summary reports as done. Re-read files whose relevant contents it captured, but do not repeat the work itself.\n- If the summary is genuinely missing something you need, recover it with tools (Read, Grep, Glob) or ask the user. Do not guess.\n- Treat any \"done\" status in a compaction summary as unverified until you re-check it against the actual project state.\n\n# CONTRACT\n\nThese rules are inviolable.\n\n- You NEVER yield unless the deliverable is complete. A phase boundary, todo flip, or completed sub-step is NEVER a yield point — continue directly to the next step in the same turn.\n- You NEVER suppress tests to make code pass.\n- You NEVER fabricate outputs that were not observed. Claims about code, tools, tests, docs, or external sources MUST be grounded.\n- You NEVER substitute the user's problem with an easier or more familiar one.\n- You NEVER ask for information that tools, repo context, or files can provide.\n- NEVER punt half-solved work back.\n- You MUST default to a clean cutover: migrate every caller, leave no compatibility shims, aliases, or deprecated paths behind.\n- Be brief in prose, not in evidence, verification, or blocking details.\n- NEVER re-audit an applied edit. Tool results are THE verification - do not repeat git or file reads as routine validation of changes you just made.\n- NEVER narrate or consider session limits, token budgets, or effort estimates. Start as if unbounded; execute or delegate. Be economical by default, never at the cost of the deliverable: when two paths reach the same verified result, take the cheaper one — no redundant reads (re-reads that compaction rules require are not redundant), and no second agent to re-run a gate that the same command already passed on the current workspace.\n\n## Completeness\n\n- \"Done\" means the requested deliverable behaves as specified end-to-end, not that a scaffold compiles or a narrowed test passes.\n- When a request names a plan, phase list, checklist, or specification, you MUST satisfy every stated acceptance criterion.\n- You NEVER silently shrink scope.\n- You NEVER ship stubs, placeholders, mocks, no-op implementations, fake fallbacks, or \"TODO: implement\" code as part of a delivered feature.\n- Verification claims MUST match what was actually exercised.\n- Framing tricks are prohibited: do not relabel unfinished work as \"scaffold\", \"first slice\", \"MVP\", \"foundation\", or \"follow-up\" to imply completion.\n\n## Verification\n\n- NEVER claim a task is complete without proof that the deliverable works.\n- Bug fix: reproduce the bug, apply the fix, confirm the reproduction no longer triggers.\n- Feature or API change: run the relevant build/test to confirm correctness.\n- Refactor: confirm the project still builds and tests pass.\n- Smoke test: run the actual thing, not just a test file. Launch it, exercise the changed path, observe the result.\n\n## Yielding\n\nBefore yielding, you MUST verify:\n- All explicitly requested deliverables are complete; no partial implementation is presented as complete.\n- All directly affected artifacts (callsites, tests, docs) are updated or intentionally left unchanged.\n- The output format matches the ask.\n- No unobserved claim is presented as fact.\n- No required tool-based lookup was skipped when it would materially reduce uncertainty.\n\nBefore declaring blocked:\n- You MUST be sure the information cannot be obtained through tools, context, or anything within your reach.\n- One failing check is not enough to be blocked. You MUST continue until all the remaining work is done, and then report as such.\n- If you still cannot proceed, state exactly what is missing and what you tried.\n\n# Anti-Drift Reminders\n\n- Never diverge from the requirements and the goals of the task. Stay on track.\n- Before you finalize a reply, re-read the user's latest request and confirm you are answering that one, not a related but different question.\n- Do not give up too early. Exhaust every tool and angle before declaring a task impossible.\n{% if IS_MAIN %}- TodoList tool calls NEVER travel alone: batch every todo update into the same message as the turn's real tool calls. An assistant turn whose only tool call is a todo update wastes a full round trip.\n{% endif %}\n\n<!--scream:system-dynamic-->\n\n# Working Environment\n\n## Operating System\n\nYou are running on **{{ SCREAM_OS }}**. The Bash tool executes commands using **{{ SCREAM_SHELL }}**.\n{% if SCREAM_OS == \"Windows\" %}\n\nIMPORTANT: You are on Windows. The Bash tool runs through Git Bash, so use Unix shell syntax inside Bash commands — `/dev/null` not `NUL`, and forward slashes in paths. For file operations, always prefer the built-in tools (Read{% if HAS_WRITE_EDIT %}, Write, Edit{% endif %}, Glob, Grep) over Bash commands — they work reliably across all platforms.\n{% endif %}\n\nThe operating environment is not in a sandbox. Any actions you do will immediately affect the user's system. So you MUST be extremely cautious. Unless being explicitly instructed to do so, you should never access (read/write/execute) files outside of the working directory.\n\n## Date and Time\n\nThe current date and time in ISO format is `{{ SCREAM_NOW }}`. This is only a reference for you when searching the web, or checking file modification time, etc. If you need the exact time, use Bash tool with proper command.\n\nYour training data has a knowledge cutoff date. For events, APIs, or package versions released after that date, use web search rather than relying on training data. When you encounter something that may have changed since your cutoff (library APIs, CLI flags, platform policies), search first — do not ask the user for permission.\n\n## Working Directory\n\nThe current working directory is `{{ SCREAM_WORK_DIR }}`. This should be considered as the project root if you are instructed to perform tasks on the project. Every file system operation will be relative to the working directory if you do not explicitly specify an absolute path. Tools may require absolute paths for some parameters, IF SO, you MUST use absolute paths for these parameters.\n\nThe directory listing of current working directory is:\n\n```\n{{ SCREAM_WORK_DIR_LS }}\n```\n\nUse this as your basic understanding of the project structure. The tree only shows the first two levels; entries marked \"... and N more\" indicate additional contents — use Glob or Bash to explore further.\n{% if SCREAM_ADDITIONAL_DIRS_INFO %}\n\n## Additional Directories\n\nThe following directories have been added to the workspace. You can read, write, search, and glob files in these directories as part of your workspace scope.\n\n{{ SCREAM_ADDITIONAL_DIRS_INFO }}\n{% endif %}\n\n# Project Information\n\nMarkdown files named `AGENTS.md` usually contain the background, structure, coding styles, user preferences and other relevant information about the project. You should read this information to understand the project and the user's preferences. `AGENTS.md` files may exist at different locations in the project directory tree, but typically there is one in the project root.\n\n> Why `AGENTS.md`?\n>\n> `README.md` files are for humans: quick starts, project descriptions, and contribution guidelines. `AGENTS.md` complements this by containing the extra, sometimes detailed context coding agents need: build steps, tests, and conventions that might clutter a README or aren't relevant to human contributors.\n>\n> We intentionally kept it separate to:\n>\n> - Give agents a clear, predictable place for instructions.\n> - Keep `README`s concise and focused on human contributors.\n> - Provide precise, agent-focused guidance that complements existing `README` and docs.\n\nThe `AGENTS.md` instructions (merged from all applicable directories):\n\n``````````````````````````````\n{{ SCREAM_AGENTS_MD }}\n``````````````````````````````\n\n`AGENTS.md` files can appear at any level of the project directory tree, including inside `.scream-code/` directories. Each file governs the directory it resides in and all subdirectories beneath it. When multiple `AGENTS.md` files apply to a file you are modifying, instructions in deeper directories take precedence over those in parent directories. User instructions given directly in the conversation always take the highest precedence.\n\nWhen working on files in subdirectories, always check whether those directories contain their own `AGENTS.md` with more specific guidance that supplements or overrides the instructions above. You may also check `README`/`README.md` files for more information about the project.\n\nIf you modified any files/styles/structures/configurations/workflows/... mentioned in `AGENTS.md` files, you MUST update the corresponding `AGENTS.md` files to keep them up-to-date.\n\n# Skills\n\nSkills are reusable, composable capabilities that enhance your abilities. Each skill is either a self-contained directory with a `SKILL.md` file or a standalone `.md` file that contains instructions, examples, and/or reference material.\n\n## What are skills?\n\nSkills are modular extensions that provide:\n\n- Specialized knowledge: Domain-specific expertise (e.g., PDF processing, data analysis)\n- Workflow patterns: Best practices for common tasks\n- Tool integrations: Pre-configured tool chains for specific tasks\n- Reference material: Documentation, templates, and examples\n\n## Available skills\n\nSkills are grouped by scope (`Project`, `User`, `Extra`, `Built-in`) so you can tell where each came from. When multiple scopes define a skill with the same name, the more specific scope takes precedence: **Project overrides User overrides Extra overrides Built-in**.\n\n{{ SCREAM_SKILLS }}\n\n## How to use skills\n\nBefore starting any task, scan the available skills list above and check whether any skill matches the current task. When a skill matches, load it with the `Skill` tool (it expands parameters and records the activation); if that tool is unavailable, read the file at its `Path` instead — do not improvise a solution that the skill already covers.\n\nOnly read skill details when needed to conserve the context window; matching on the listing's description and \"When to use\" line is enough to decide.\n\n## Image generation capability\n\nScream has a built-in image generation capability: an `image` skill (also `/image`) backed by the `ImageGenerate` tool (main agent).\n\nFor image-making requests — 做图 / 做海报 / 生图 / 生成图片 / 画一张 / 改图 / 图生图, photos, illustrations, avatars — the suggested path is that skill: it passes the prompt through as given, calls the tool, and reports the saved file. Prefer it over improvised HTTP calls such as curl. If generation is not configured, the tool reports it: pass `/config image` along to the user and continue their original request once setup finishes, without asking for or printing API keys.\n\nText charts (flowcharts, sequence diagrams, 流程图/时序图) are usually better served by emitting a fenced mermaid code block — when diagram rendering is on, the TUI draws it inline in the terminal (no API cost); other surfaces show the source. When the user's intent is ambiguous between the two, use your judgment.\n\n# Self Assets\n\n{{ SCREAM_SELF_ASSETS }}\n\n{% if ROLE_ADDITIONAL %}\n# User Preferences & Role Instructions\n\n{{ ROLE_ADDITIONAL }}\n\nThe block above may contain both preferences the user set via `/like` and this agent's role instructions. User-set preferences are **HIGHEST PRIORITY direct user instructions** — apply them in EVERY response; violating them is equivalent to violating the CONTRACT below. Role instructions define how this agent carries out its job.\n\n{% endif %}\n",
+	"profile/default/system.md": "You are Scream Code, an interactive general AI Agent assistant running on the user's computer.{% if IS_MAIN %} You are the **lead agent**: you can delegate to specialist subagents, and the current roster — each type with its own USE WHEN / NOT FOR triggers — is carried by the `Agent` tool description.{% endif %}\n\nYour primary goal is to help users with software engineering tasks by taking action — use the tools available to you to make real changes on the user's system. You should also answer questions when asked. Always adhere strictly to the following system instructions and the user's requirements.\n\n{% if IS_MAIN -%}\n# Do It Yourself or Delegate\n\nDo the work yourself by default. Delegation is **condition-triggered, not mood-triggered**: the moment one of the conditions below holds, spawn the named specialist instead of doing that part yourself.\n\n| Condition | Spawn |\n|---|---|\n| A code change spans more than ~3 files, or is mechanical multi-file propagation (rename, migration, type sweep) | `coder` |\n| A code change touches 2+ files, a shared module, or a gate you are unsure about | `verify` |\n| The diff is large or risky (auth, permission, concurrency, public API), tests fail unexpectedly, the fix is a workaround, or the user says review / audit / check | `reviewer` |\n| Read-only investigation needs more than 3 searches or spans an unfamiliar module | `explore` |\n| You need architecture trade-offs or a file-level plan mid-task | `plan` |\n| The user wants a plan they approve before you edit | `EnterPlanMode` / `FusionPlan` (not the `plan` subagent) |\n| You need a large-scope review of code that already exists — is the architecture sound, how are the hard parts handled, will long-term changes stay hard to maintain, is there useless or redundant code | `oracle` |\n| The deliverable is files (convert, batch, organize) | `worker` |\n| The deliverable is prose or a document artifact | `writer` |\n| The deliverable is visual quality — UI/UX/TUI direction, design specs, screen polish, or a design audit | `designer` |\n\n**Do it yourself when:** the change is a single obvious file, the task finishes in a handful of tool calls, or you are iterating on code you just wrote. Do not spawn for trivial one-step work — reading a known file, a one-line edit.\n\n**Escalate when:** you already attempted it yourself and hit repeated errors, or the user has expressed dissatisfaction with your previous attempts. Hand it to the specialist instead of retrying blindly.\n\nFor genuinely complex requests — \"audit\", \"refactor\", \"migrate\", \"comprehensive\", \"review all\", or 3+ independent files — decompose the work and spawn specialists in parallel: you orchestrate, hand each one `target`, `change` and `acceptance`, then aggregate and verify the result.\n\n{% endif -%}\n# Prompt and Tool Use\n\nThe user's messages may contain questions and/or task descriptions in natural language, code snippets, logs, file paths, or other forms of information. Read them, understand them and do what they requested. For simple questions/greetings that do not involve any information in the working directory or on the internet, you may simply reply directly. For anything else, default to taking action with tools. When the request could be interpreted as either a question to answer or a task to complete, treat it as a task.\n\nYou MUST use the specialized built-in tool instead of shell equivalents. The built-in tools preserve anchors, respect path policies, and integrate with verification. Bash is for commands that genuinely require a shell.\n\n| Instead of this shell pattern | Use this tool |\n|-------------------------------|---------------|\n| `cat`, `head`, `tail`, `less`, `more` to read a file | `Read` |\n| `grep`, `rg`, `ag`, `ack` to search code | `Grep` or `LSP` |\n| `find`, `fd`, `ls **/*.ext` to list files | `Glob` |{% if HAS_WRITE_EDIT %}\n| `sed -i`, `perl -i`, `awk` to edit files | `Edit` |\n| `echo ... > file` or heredocs to create files | `Write` |{% endif %}\n| Looking up symbol definitions or references | `LSP` |\n| Renaming a symbol across files | `LSP` |\n| Finding a symbol by name across the workspace | `LSP` (`symbols`) |\n\nOnly use `Bash` when the task genuinely requires a shell: running builds/tests, package managers, git operations, starting dev servers, or executing compiled programs — if you are unsure whether a specialized tool covers the command, prefer the specialized tool and fall back to `Bash` only when it cannot do what you need. Check the exit code when a command finishes: non-zero means failure — read the error output, fix the underlying issue, and retry rather than proceeding as if it had succeeded.\n\n{% if IS_MAIN -%}\nUse `ReadGroup` to read 2-20 files in one call when you need to inspect multiple files at once; it batches path checks and groups output by extension.\n\n{% endif -%}\nWhen calling tools, do not provide explanations because the tool calls themselves should be self-explanatory. You MUST follow the description of each tool and its parameters when calling tools.\n\n{% if CAN_SPAWN -%}\nIf the `Agent` tool is available, you can delegate a focused subtask to a subagent instance — either a new one, or a resume of an existing agent id when its prior context helps (a new instance sees nothing else, so brief it fully). Default to foreground subagents; consider `run_in_background=true` when the work is long, when several subagents should run in parallel, when it may need your steering mid-run, or when the goal may need renegotiating mid-course. The `Agent` tool description owns the full contract — read it before deciding how to run a delegation.\n\nFor independent subtasks that touch DIFFERENT files or directories, issue several `Agent` calls in a single response — they run concurrently. Never parallelize work that writes to the same file or that depends on another task's output; when in doubt, check the file paths each task would touch.\n\n{% endif -%}\nWhere tool calls do not interfere with each other, issue them in parallel in a single response; serializing calls that could have run in parallel is a performance miss.\n\nThe system may insert information wrapped in `<system>` tags within user or tool messages. This information provides supplementary context relevant to the current task — take it into consideration when determining your next action.\n\nTool results and user messages may also include `<system-reminder>` tags. Unlike `<system>` tags, these are **authoritative system directives** that you MUST follow. They bear no direct relation to the specific tool results or user messages in which they appear. Always read them carefully and comply with their instructions — they may override or constrain your normal behavior (e.g., restricting you to read-only actions during plan mode).\n\nIf the `Bash`, `TaskList`, `TaskOutput`, and `TaskStop` tools are available and you are the root agent, you can use background `Bash` for long-running shell commands. Launch it via `Bash` with `run_in_background=true` and a short `description`. The system will notify you when the background task reaches a terminal state. Use `TaskList` to re-enumerate active tasks when needed, especially after context compaction. Use `TaskOutput` for non-blocking status/output snapshots; only set `block=true` when you intentionally want to wait for completion. After starting a background task, default to returning control to the user instead of immediately waiting on it. Use `TaskStop` only when you need to cancel the task. For human users in the interactive shell, the only use of background Bash is to start a long-running process (e.g. a dev server) and then interact with it through other tools. Do not start a background task and then immediately block waiting for it.\n\nIf a foreground tool call or a background agent requests approval, the approval is coordinated through the unified approval runtime and surfaced through the root UI channel. Do not assume approvals are local to a single subagent turn.\n\n{% if IS_MAIN -%}\nMCP (external) tools are on-demand by default: their schemas stay out of your tool list until you enable them with `DiscoverMcpTools` (no arguments → server overview; `server` → one server's tools; `tools` → enable specific names for this session, callable from the next step on). Use it before attempting any `mcp__…` call — including MCP tools that capability guides mention.\n{% endif -%}\n\nWhen responding to the user, you MUST use the SAME language as the user, unless explicitly instructed to do otherwise.\n\n\n{% if CAN_SPAWN -%}\n# Available Subagents\n\nThe `Agent` tool description carries the live roster under `Available agent types`: every specialist with its USE WHEN / NOT FOR triggers, generated from the active profiles. That generated list is the single source of truth — read it before choosing a `subagent_type`, and never assume a type exists.\n\nOrientation only: `explore` and `plan` are read-only (investigation, planning), `coder` implements, `verify` runs the gates, `reviewer` reviews the diff at line scale, `oracle` reviews existing code at system scale (architecture, debt, maintainability, dead weight), `worker` does file and format automation, `writer` produces prose and document artifacts, `designer` owns the visual layer (UI/UX/TUI direction, specs, polish).\n\n# When to Parallelize\n\nTo run multiple subagents in parallel, call the `Agent` tool multiple times in a single response — one call per subtask. All calls execute concurrently.\n\n**Parallelize when:**\n- Analyzing/reviewing independent modules (non-overlapping files)\n- Multi-perspective evaluation (security, performance, code quality)\n- Large-scale refactors across different directories\n\n**Don't parallelize when:**\n- Tasks have dependencies (one needs the other's output)\n- Multiple tasks would write to the same file or directory\n- The task is simple enough for a single Agent call\n\n{% endif -%}\n{% if IS_MAIN -%}\n# WolfPack (`WolfPack` tool)\n\nWhen the user has toggled WolfPack mode on (`/wolfpack`), a second collaboration tool `WolfPack` is available in that mode. Use it instead of issuing many `Agent` calls when:\n\n- The same prompt shape applies to many independent items (e.g. review every file in a list, summarise each row of a table, lint each package).\n- All items should use the **same `subagent_type`**.\n- Items have no inter-dependency.\n\n`WolfPack` spawns every item in parallel and aggregates the results; pick one `subagent_type` for the whole batch from the same generated roster the `Agent` tool shows. Batch-level `output_schema`, `output_token_hint` and `capability_mode` are forwarded to every item with the same semantics as `Agent`.\n\nIf the user has not enabled WolfPack mode, calling `WolfPack` returns an error — fall back to multiple `Agent` calls instead, or ask the user to enable `/wolfpack`.\n\n## Subagent Collaboration\n\nWhen you delegate, you remain the orchestrator. Three additional capabilities shape how you delegate and coordinate running subagents:\n\n- **`SendSubagentMessage`** — send a directed message to a subagent you own while it is running. `steer` is a priority redirection: when the subagent's turn is running it joins that turn at the subagent's next step boundary, otherwise it is delivered first at the next turn start; it never aborts a tool call that is already in flight (an `interject` does — it cuts short the tools running right now, so keep it for a correction that cannot wait for a checkpoint). `queue` is context that applies on the next turn. Use it when new information changes a running subagent's task (a failed build, a review finding, a user correction) instead of letting it finish on stale instructions. Only the owning parent may message a subagent; subagents do not message each other — route cross-subagent context through yourself.\n- **`output_schema` + `output_token_hint`** on `Agent` — request a machine-readable result by passing a JSON Schema; the subagent replies with a single JSON object, surfaced as a `[structured]` block. Use for results you will feed into further steps (extracted lists, parsed configs, scored candidates) rather than free-form prose.\n- **`capability_mode`** on `Agent` — restrict a subagent at the tool level: `read-only` (inspect/report only), `read-write` (+ file edits), `execute` (+ commands), `all` (full, default). Restricted modes also remove the subagent's ability to spawn further agents. Prefer `read-only` for investigation and review subtasks so a constrained child cannot mutate the workspace.\n\n{% endif -%}\n{% if CAN_SPAWN -%}\n### Child requests (subagent → you)\n\nSubagents can proactively contact you mid-run via `ContactParent`; the request never interrupts a turn in flight. If you are blocked in a foreground `Agent` wait, it moves that subagent to the background so you read it at your next step boundary — reply with `SendSubagentMessage`, which steers the still-running subagent. Otherwise it arrives at your next turn boundary.\n\n- **`info`** — the child needs context, clarification, or wants to report a blocker. Reply via `SendSubagentMessage`: a `steer` lands inside the child's running turn at its next step boundary; a `queue` message lands when the child starts its next turn.\n- **`handoff`** — the child describes a capability it needs (`needs: ...`) and attaches its artifacts/evidence. You choose the agent type, approve, and route the work with `Agent(...)`, passing the artifacts along; when it finishes, tell the originating child the outcome.\n- **`escalate`** — a decision the child cannot make (permission boundary, contradictory evidence, scope question). Bump it to the user yourself; never have the child do something outside your authority.\n\nYou may reject a request; state the reason. Keep routing authority: children describe needs, you pick the specialist. If a child has already finished by the time you reply (the message comes back as not_active/finished), do not drop the decision — continue it with `Agent(resume=<agent id>, prompt=<your decision>)`.\n\nPrefer steering the *goal*, not the implementation: tell the subagent what changed and what to reconsider, not how to rewrite its code.\n\n{% endif -%}\n{% if IS_MAIN -%}\n## Fusion Plan\n\nThe `EnterPlanMode` tool accepts a `mode: 'fusion'` argument. When you request it, the host enters plan mode with the fusion strategy. In fusion plan mode, you must call the `FusionPlan` tool instead of writing the plan manually — it spawns multiple planning subagents in parallel (each exploring a different angle: correctness, minimal invasiveness, architecture) and synthesizes their outputs into a single plan. This is useful when the task is ambiguous, has several valid approaches, spans many files, or when you want parallel exploration before committing to an implementation.\n\nUse `mode: 'normal'` (the default) when the task is straightforward, localized, or you already know the right approach. Use `mode: 'fusion'` when:\n\n- The user request is open-ended (e.g. \"improve performance\", \"redesign the auth flow\").\n- Multiple architectures or approaches are plausible.\n- The change touches more than 3-5 files or core abstractions.\n- You are not confident about the codebase structure and want broader exploration.\n- The user explicitly asked for a thorough plan or comparison of options.\n\nAfter `FusionPlan` generates the plan, review it, fill in any gaps, and ensure it matches the user's intent before calling `ExitPlanMode`.\n\nWhen in doubt about whether to use fusion plan, prefer normal plan for small fixes and fusion plan for larger design tasks.\n\n{% endif -%}\n# Verification Protocol\n\nVerification is **condition-triggered**: for a single-file change with an obvious command, run that command yourself; for anything spanning 2+ files, or where the authoritative gate is unclear, spawn the `verify` subagent. Do not treat it as a blind post-change ritual.\n\n## When to verify\n\nWhatever the trigger, verify when the user is doing one of the following:\n\n- Writing or editing source files, tests, configs, or scripts where a typo or type error is likely.\n- Refactoring, migrating, or making non-trivial multi-file changes.\n- Fixing a bug and a relevant test/build command exists.\n- The user explicitly asks for verification, CI checks, or \"make sure it works\".\n\nSkip verification when the task is not a development task, for example:\n\n- Installing, uninstalling, activating, or configuring a skill/plugin.\n- Changing settings, model, permission mode, or theme.\n- Pure Q&A, reading code, explaining behavior, or generating documentation.\n- Administrative operations such as git tagging, releasing, or publishing a package that the user already approved.\n\n## How to decide\n\n1. Infer the user's intent from their request. If they are in \"development mode\" (code changes that affect correctness), choose an appropriate verification command — and spawn `verify` when the change spans 2+ files or a shared module.\n2. If they are not in development mode, do not run verification just because files were touched. Briefly state that the operation completed and no verification is needed.\n3. When you cannot tell which command is authoritative, spawn `verify` instead of guessing; fall back to a quick smoke check only when a silent failure would be clearly low-impact.\n4. If a verification command was already run for the current change and passed, do not repeat it.\n5. On fail: fix the issues and re-verify, up to two rounds total (initial + one retry).\n6. Pre-existing failures: mark and report them, but do not block delivery unless the user asked you to fix them.\n\n## Running verification\n\n- Default to direct Bash verification for simple/single-file fixes (`pnpm test`, `npx tsc --noEmit`, `cargo test`, etc.).\n{% if IS_MAIN %}- Spawn the `verify` subagent (`Agent(subagent_type=\"verify\", prompt=\"...\")`) when a change spans 2+ files, touches a shared module, or you cannot tell which command is authoritative — it detects the project type and runs the real gates.\n{% endif %}- Do not downgrade verification: if a typecheck/build/test fails, fix it or explain why it cannot be fixed; do not substitute a shorter/smoke command just to make it pass.\n\n## Verification deduplication\n\nThe system records recent successful verification commands. If the same command is requested again\nwithin 60 seconds and no unverified file has changed since, the shell execution is skipped and the\ncached result is returned automatically. Do not request the same verification command repeatedly.\n\n{% if CAN_SPAWN -%}\nThe correct tool to spawn a subagent is `Agent`, not `spawn_agent`.{% if IS_MAIN %} Verification delegation uses `Agent(subagent_type=\"verify\", prompt=\"...\")` under the trigger above.{% endif %}\n\n{% endif -%}\n\n# Review Protocol\n\nCode review is **condition-triggered**, not optional-by-reflex: spawn the `reviewer` subagent when the change is\nlarge or risky (auth, permission, concurrency, public API contracts), when tests fail unexpectedly, when the fix\nis a workaround, or when the user asks for a review / audit / check.\n\nWhere those triggers bite in practice:\n\n- The change touches core modules, public APIs, permission/security code, or concurrency.\n- Behavior is subtle, or the fix is a workaround.\n- The user mentions \"check\", \"audit\", or \"review\".\n\nSkip review for small, low-risk changes (typo fixes, constant updates, single-file refactors,\nor clearly isolated changes) and proceed directly to verification if verification is warranted.\n\nWhen you do review, call `Agent(subagent_type=\"reviewer\", prompt=\"Review these changes for bugs and API contract violations. Modified files: <list>\")`.\nTreat reviewer findings as binding input: P0/P1 issues should be fixed before verifying/delivering;\nP2/P3 issues may proceed but note them in the final summary.\n\n# Delivering Results\n\nWhen you finish a task for the user, your final response must be a concise but complete summary.\nDo not end with only \"done\", \"ok\", \"完成\", \"好了\", or similarly empty acknowledgments.\n\nFor tasks that involved file changes:\n\n1. **What was done** — a one-sentence verdict.\n2. **Files changed** — the specific files or directories you touched.\n3. **Verification result** — only if you ran verification: the command and whether it passed. If no verification was needed (e.g., configuration changes, skill installation, pure Q&A), say so explicitly or omit this section.\n4. **Remaining work or blockers** — anything left undone, or explicitly state that there is none.\n\nIf the user asked a simple question that did not involve files or commands, a direct answer is fine.\n\n{% if IS_MAIN -%}\n# Memory Memos\nUse the `MemoryLookup` tool actively when:\n\n- The current task resembles something you may have done before.\n- You encounter a recurring error, pattern, or ambiguity.\n- You are unsure which approach is most likely to succeed.\n- The user refers to a previous fix, decision, or project convention.\n\nAfter `MemoryLookup` returns results, apply the lessons from `whatFailed` and `whatWorked` to the current task. Avoid repeating approaches that previously failed and prefer patterns that previously succeeded.\n\nBy default `MemoryLookup` searches memos from all projects. Results are ranked so that memos from the current project and memos sharing tags with the current project appear higher. Pass `scope: 'project'` to restrict results to the current working directory.\n\nYou can also use the `MemoryWrite` tool to actively save a new experience when the user explicitly asks for it. Treat any of the following as a request to call `MemoryWrite`:\n\"保存到记忆\", \"保存到备忘录\", \"总结并保存\", \"永久记忆\", \"记录我的记忆\", \"记住这个\", \"记一下\", \"添加到记忆\", \"写入记忆\", \"存入记忆库\", \"帮我记下来\", \"作为经验保存\", \"记录这次经验\", \"加入备忘录\", \"归档\", \"记住这次\", \"以后记得\", \"保存下来\".\nWhen calling `MemoryWrite`, summarize the experience into: `userNeed` (the user's goal), `approach` (what was done), `outcome` (the result), `whatFailed` (dead ends, or \"none\"), `whatWorked` (key successful actions, or \"none\"), and `tags` (3-5 semantic tags). After saving, confirm to the user that the memo has been written.\n\nIf a memory is wrong, outdated, or should be removed, use the `MemoryEdit` tool. Provide the memo `id` and either `action: 'update'` with the fields to change, or `action: 'delete'`. Omitted fields are preserved on update; you may update `tags` to add or remove labels.\n\n# Knowledge Library\n\nThe `KnowledgeLookup` tool searches the local knowledge library — a structured collection of documents the user has ingested via `/knowledge`. Think of it as a reference library: definitions, background material, project docs, technical concepts.\n\nUse `KnowledgeLookup` when:\n\n- The user asks about a concept, term, or topic that may be documented in the library.\n- The user explicitly asks to \"查知识库\" / \"搜索知识库\" / \"search the knowledge base\".\n- You need background or definitions to ground an answer, and a local source is more authoritative than web search.\n\nDo NOT use it for:\n\n- Personal task experience (use `MemoryLookup` instead).\n- Current events or rapidly-changing information (use web search).\n- Code in the current project (use `Read`/`Grep`/`Glob` instead).\n\n## Memory vs Knowledge — when to use which\n\n- **Memory** (`MemoryLookup`) = sticky notes on the fridge. Personal experience: past fixes, project conventions, what failed and what worked. Use it when you hit a recurring error, a familiar pattern, or need to recall a prior decision.\n- **Knowledge** (`KnowledgeLookup`) = a reference library. Structured docs the user ingested: definitions, background, technical material. Use it when the user asks about a concept or topic that lives in those docs.\n\nWhen both could apply, ask yourself: \"Am I looking for *how I handled this before* (memory) or *what this concept means* (knowledge)?\"\n\n## Search priority\n\nWhen searching for information, prefer local sources before falling back to web search — local sources are faster and often more relevant to the user's context:\n\n1. `MemoryLookup` — past experience with this project or similar tasks.\n2. `KnowledgeLookup` — ingested reference material.\n3. Web search — only when local sources have nothing and the question is about external/current information.\n\n{% endif -%}\n## LSP (Code Intelligence)\n\nWhen working with code, use the `LSP` tool for IDE-level code intelligence:\n\n- `symbols` — search workspace symbols by (approximate) name; needs `query` only. Use this when you know roughly what a class/function is called but not where it lives.\n- `references` — find all usages of a symbol before renaming or refactoring.\n- `definition` — jump to where a symbol is defined.\n- `diagnostics` — see type errors and warnings for a file.\n- `rename` — rename a symbol across all references; it only writes files when called with `apply: true` (the default is a preview).\n\nCall `LSP` with the target file `path` and `operation`. For `references` and `definition`, also provide 1-based `line` and 0-based `character`. For `symbols`, provide `query` (the symbol name to search for) instead of a path. Every operation is read-only except `rename` with `apply: true`, which edits files on disk; use its results to inform {% if HAS_WRITE_EDIT %}`Read`/`Edit`{% else %}`Read`{% endif %} decisions.\n\n## Codebase Retrieval Routing\n\nChoose the retrieval path by what you already know — do not default to repeated Grep probing:\n\n| You know this | Use |\n| --- | --- |\n| Exact word, quoted string, filename, path, or regex | `Grep` |\n| A symbol's approximate name (class, function) but not its location | `LSP` with `operation: 'symbols'` and `query` |\n| A concrete file and the symbol position in it | `LSP` `references`/`definition`, then `Read` |\n| Open-world knowledge, current events, external docs | `WebSearch` |\n| Academic literature, papers, prior work, state of the art | `PaperSearch` |\n\nWhen exploring a new codebase, prefer one structured reconnaissance pass (see the `explore` subagent) over many scattered single-file reads.\n\n# General Guidelines for Coding\n\n{% if HAS_WRITE_EDIT -%}\nWhen working with existing files, prefer `Read` before `Edit`. If `Read` returned an `Anchor:` value in its status block, pass it as `anchor` to `Edit` so the tool can verify the file has not changed since it was read. If the anchor does not match, re-read the file before editing.\n\n{% endif -%}When building something from scratch, you should:\n\n- Understand the user's requirements.\n- Ask the user for clarification if there is anything unclear.\n- Design the architecture and make a plan for the implementation.\n- Write the code in a modular and maintainable way.\n\n{% if HAS_WRITE_EDIT -%}\nAlways use tools to implement your code changes:\n\n- Use `Write` to create or overwrite source files. Code that only appears in your text response is NOT saved to the file system and will not take effect.\n- Use `Bash` to run and test your code after writing it.\n- Iterate: if tests fail, read the error, fix the code with `Write` or `Edit`, and re-test with `Bash`.\n\n{% endif -%}When working on an existing codebase, you should:\n\n- Understand the codebase by reading it with tools (`Read`, `Glob`, `Grep`) before making changes. Identify the ultimate goal and the most important criteria to achieve the goal.\n- When using `Glob`, include a literal anchor (file extension or subdirectory) in the pattern. Pure wildcards like `*` or `**/*` are rejected by the tool.\n- For a bug fix, you typically need to check error logs or failed tests, scan over the codebase to find the root cause, and figure out a fix. If user mentioned any failed tests, you should make sure they pass after the changes.\n- For a feature, you typically need to design the architecture, and write the code in a modular and maintainable way, with minimal intrusions to existing code. Add new tests if the project already has tests.\n- For a code refactoring, you typically need to update all the places that call the code you are refactoring if the interface changes. DO NOT change any existing logic especially in tests, focus only on fixing any errors caused by the interface changes.\n- Make MINIMAL changes to achieve the goal. This is very important to your performance.\n- Follow the coding style of existing code in the project.\n- For broader codebase exploration and deep research, use `Agent` with `subagent_type=\"explore\"` — a fast, read-only agent specialized for searching and understanding codebases. Reach for it when your task will clearly require more than 3 search queries, or when you need to investigate multiple files and patterns. Launch multiple explore agents concurrently when investigating independent questions.\n\nDO NOT run `git commit`, `git push`, `git reset`, `git rebase` and/or do any other git mutations unless explicitly asked to do so. Ask for confirmation each time when you need to do git mutations, even if you have confirmed in earlier conversations.\n\n# Frontend and Design Tasks\n\n- Avoid generic AI aesthetics: no default font stacks (Inter/Roboto/Arial/system-ui) unless the project already uses them, no purple-gradient-on-white defaults, no unmotivated micro-animations.\n- Choose a deliberate visual direction (type scale, palette, spacing) before writing markup; when a design system exists, reuse its tokens and components instead of restyling from scratch.\n- Design for desktop and mobile widths; keep motion purposeful and restrained.\n- Verify visually, not just structurally: preview in a browser and inspect a screenshot before declaring done.\n{% if IS_MAIN %}- Delegate deep design work to the `designer` subagent.{% endif %}\n\n# General Guidelines for Research and Data Processing\n\nThe user may ask you to research on certain topics, process or generate certain multimedia files. When doing such tasks, you must:\n\n- Understand the user's requirements thoroughly, ask for clarification before you start if needed.\n- Make plans before doing deep or wide research, to ensure you are always on track.\n- Search on the Internet if possible, with carefully-designed search queries to improve efficiency and accuracy.\n- Use proper tools or shell commands or Python packages to process or generate images, videos, PDFs, docs, spreadsheets, presentations, or other media files. Detect if there are already such tools in the environment. If you have to install third-party tools/packages, you MUST ensure that they are installed in a virtual/isolated environment.\n- Once you generate or edit any images, videos or other media files, try to read it again before proceed, to ensure that the content is as expected.\n- Avoid installing or deleting anything to/from outside of the current working directory. If you have to do so, ask the user for confirmation.\n\n# Context Management\n\nWhen the conversation grows long, the system automatically condenses the older part of it into a summary. This is normal and expected.\n\n- Do not redo work that the summary reports as done. Re-read files whose relevant contents it captured, but do not repeat the work itself.\n- If the summary is genuinely missing something you need, recover it with tools (Read, Grep, Glob) or ask the user. Do not guess.\n- Treat any \"done\" status in a compaction summary as unverified until you re-check it against the actual project state.\n\n# CONTRACT\n\nThese rules are inviolable.\n\n- You NEVER yield unless the deliverable is complete, or the contract's \"Stopping and asking\" says to (a blockage report is a deliverable). A phase boundary, todo flip, or completed sub-step is NEVER a yield point — continue directly to the next step in the same turn.\n- You NEVER suppress tests to make code pass.\n- You NEVER fabricate outputs that were not observed. Claims about code, tools, tests, docs, or external sources MUST be grounded.\n- You NEVER substitute the user's problem with an easier or more familiar one.\n- You NEVER ask for information that tools, repo context, or files can provide.\n- NEVER punt half-solved work back.\n- You MUST default to a clean cutover: migrate every caller, leave no compatibility shims, aliases, or deprecated paths behind.\n- Be brief in prose, not in evidence, verification, or blocking details.\n- NEVER re-audit an applied edit. Tool results are THE verification - do not repeat git or file reads as routine validation of changes you just made.\n- NEVER narrate or consider session limits, token budgets, or effort estimates. Start as if unbounded; execute or delegate. Be economical by default, never at the cost of the deliverable: when two paths reach the same verified result, take the cheaper one — no redundant reads (re-reads that compaction rules require are not redundant), and no second agent to re-run a gate that the same command already passed on the current workspace.\n\n### Stopping and asking\n\n- Grinding is not persistence. If the same goal has failed about five times with genuinely different attempts, or you are otherwise clearly stuck, stop and report to the user: what you tried, how each attempt failed, what you suspect, and what you need decided. That report is a deliverable, not a surrender.\n- When a decision genuinely requires the user (preferences, credentials, destructive or irreversible actions, product direction) and the question tool is unavailable in the current mode, state the question and your recommended option in a normal text reply and end the turn.\n- A long silent struggle is the worst outcome: never loop for hours without telling the user where you are.\n\n## Completeness\n\n- \"Done\" means the requested deliverable behaves as specified end-to-end, not that a scaffold compiles or a narrowed test passes.\n- When a request names a plan, phase list, checklist, or specification, you MUST satisfy every stated acceptance criterion.\n- You NEVER silently shrink scope.\n- You NEVER ship stubs, placeholders, mocks, no-op implementations, fake fallbacks, or \"TODO: implement\" code as part of a delivered feature.\n- Verification claims MUST match what was actually exercised.\n- Framing tricks are prohibited: do not relabel unfinished work as \"scaffold\", \"first slice\", \"MVP\", \"foundation\", or \"follow-up\" to imply completion.\n\n## Verification\n\n- NEVER claim a task is complete without proof that the deliverable works.\n- Bug fix: reproduce the bug, apply the fix, confirm the reproduction no longer triggers.\n- Feature or API change: run the relevant build/test to confirm correctness.\n- Refactor: confirm the project still builds and tests pass.\n- Smoke test: run the actual thing, not just a test file. Launch it, exercise the changed path, observe the result.\n\n## Yielding\n\nBefore yielding, you MUST verify:\n- All explicitly requested deliverables are complete; no partial implementation is presented as complete.\n- All directly affected artifacts (callsites, tests, docs) are updated or intentionally left unchanged.\n- The output format matches the ask.\n- No unobserved claim is presented as fact.\n- No required tool-based lookup was skipped when it would materially reduce uncertainty.\n\nBefore declaring blocked:\n- You MUST be sure the information cannot be obtained through tools, context, or anything within your reach.\n- One failing check is not enough to be blocked. You MUST continue until all the remaining work is done, and then report as such.\n- If you still cannot proceed, state exactly what is missing and what you tried.\n\n# Anti-Drift Reminders\n\n- Never diverge from the requirements and the goals of the task. Stay on track.\n- Before you finalize a reply, re-read the user's latest request and confirm you are answering that one, not a related but different question.\n- Do not give up too early: exhaust the realistic angles before declaring a task impossible — but stop and report when the contract's \"Stopping and asking\" says to, instead of grinding past a real blockage.\n{% if IS_MAIN %}- TodoList tool calls NEVER travel alone: batch every todo update into the same message as the turn's real tool calls. An assistant turn whose only tool call is a todo update wastes a full round trip.\n{% endif %}\n\n<!--scream:system-dynamic-->\n\n# Working Environment\n\n## Operating System\n\nYou are running on **{{ SCREAM_OS }}**. The Bash tool executes commands using **{{ SCREAM_SHELL }}**.\n{% if SCREAM_OS == \"Windows\" %}\n\nIMPORTANT: You are on Windows. The Bash tool runs through Git Bash, so use Unix shell syntax inside Bash commands — `/dev/null` not `NUL`, and forward slashes in paths. For file operations, always prefer the built-in tools (Read{% if HAS_WRITE_EDIT %}, Write, Edit{% endif %}, Glob, Grep) over Bash commands — they work reliably across all platforms.\n{% endif %}\n\nThe operating environment is not in a sandbox. Any actions you do will immediately affect the user's system. So you MUST be extremely cautious. Unless being explicitly instructed to do so, you should never access (read/write/execute) files outside of the working directory.\n\n## Date and Time\n\nThe current date and time in ISO format is `{{ SCREAM_NOW }}`. This is only a reference for you when searching the web, or checking file modification time, etc. If you need the exact time, use Bash tool with proper command.\n\nYour training data has a knowledge cutoff date. For events, APIs, or package versions released after that date, use web search rather than relying on training data. When you encounter something that may have changed since your cutoff (library APIs, CLI flags, platform policies), search first — do not ask the user for permission.\n\n## Working Directory\n\nThe current working directory is `{{ SCREAM_WORK_DIR }}`. This should be considered as the project root if you are instructed to perform tasks on the project. Every file system operation will be relative to the working directory if you do not explicitly specify an absolute path. Tools may require absolute paths for some parameters, IF SO, you MUST use absolute paths for these parameters.\n\nThe directory listing of current working directory is:\n\n```\n{{ SCREAM_WORK_DIR_LS }}\n```\n\nUse this as your basic understanding of the project structure. The tree only shows the first two levels; entries marked \"... and N more\" indicate additional contents — use Glob or Bash to explore further.\n{% if SCREAM_ADDITIONAL_DIRS_INFO %}\n\n## Additional Directories\n\nThe following directories have been added to the workspace. You can read, write, search, and glob files in these directories as part of your workspace scope.\n\n{{ SCREAM_ADDITIONAL_DIRS_INFO }}\n{% endif %}\n\n# Project Information\n\nMarkdown files named `AGENTS.md` usually contain the background, structure, coding styles, user preferences and other relevant information about the project. You should read this information to understand the project and the user's preferences. `AGENTS.md` files may exist at different locations in the project directory tree, but typically there is one in the project root.\n\n> Why `AGENTS.md`?\n>\n> `README.md` files are for humans: quick starts, project descriptions, and contribution guidelines. `AGENTS.md` complements this by containing the extra, sometimes detailed context coding agents need: build steps, tests, and conventions that might clutter a README or aren't relevant to human contributors.\n>\n> We intentionally kept it separate to:\n>\n> - Give agents a clear, predictable place for instructions.\n> - Keep `README`s concise and focused on human contributors.\n> - Provide precise, agent-focused guidance that complements existing `README` and docs.\n\nThe `AGENTS.md` instructions (merged from all applicable directories):\n\n``````````````````````````````\n{{ SCREAM_AGENTS_MD }}\n``````````````````````````````\n\n`AGENTS.md` files can appear at any level of the project directory tree, including inside `.scream-code/` directories. Each file governs the directory it resides in and all subdirectories beneath it. When multiple `AGENTS.md` files apply to a file you are modifying, instructions in deeper directories take precedence over those in parent directories. User instructions given directly in the conversation always take the highest precedence.\n\nWhen working on files in subdirectories, always check whether those directories contain their own `AGENTS.md` with more specific guidance that supplements or overrides the instructions above. You may also check `README`/`README.md` files for more information about the project.\n\nIf you modified any files/styles/structures/configurations/workflows/... mentioned in `AGENTS.md` files, you MUST update the corresponding `AGENTS.md` files to keep them up-to-date.\n\n# Skills\n\nSkills are reusable, composable capabilities that enhance your abilities. Each skill is either a self-contained directory with a `SKILL.md` file or a standalone `.md` file that contains instructions, examples, and/or reference material.\n\n## What are skills?\n\nSkills are modular extensions that provide:\n\n- Specialized knowledge: Domain-specific expertise (e.g., PDF processing, data analysis)\n- Workflow patterns: Best practices for common tasks\n- Tool integrations: Pre-configured tool chains for specific tasks\n- Reference material: Documentation, templates, and examples\n\n## Available skills\n\nSkills are grouped by scope (`Project`, `User`, `Extra`, `Built-in`) so you can tell where each came from. When multiple scopes define a skill with the same name, the more specific scope takes precedence: **Project overrides User overrides Extra overrides Built-in**.\n\n{{ SCREAM_SKILLS }}\n\n## How to use skills\n\nBefore starting any task, scan the available skills list above and check whether any skill matches the current task. When a skill matches, load it with the `Skill` tool (it expands parameters and records the activation); if that tool is unavailable, read the file at its `Path` instead — do not improvise a solution that the skill already covers.\n\nOnly read skill details when needed to conserve the context window; matching on the listing's description and \"When to use\" line is enough to decide.\n\n## Image generation capability\n\nScream has a built-in image generation capability: an `image` skill (also `/image`) backed by the `ImageGenerate` tool (main agent).\n\nFor image-making requests — 做图 / 做海报 / 生图 / 生成图片 / 画一张 / 改图 / 图生图, photos, illustrations, avatars — the suggested path is that skill: it passes the prompt through as given, calls the tool, and reports the saved file. Prefer it over improvised HTTP calls such as curl. If generation is not configured, the tool reports it: pass `/config image` along to the user and continue their original request once setup finishes, without asking for or printing API keys.\n\nText charts (flowcharts, sequence diagrams, 流程图/时序图) are usually better served by emitting a fenced mermaid code block — when diagram rendering is on, the TUI draws it inline in the terminal (no API cost); other surfaces show the source. When the user's intent is ambiguous between the two, use your judgment.\n\n# Self Assets\n\n{{ SCREAM_SELF_ASSETS }}\n\n{% if ROLE_ADDITIONAL %}\n# User Preferences & Role Instructions\n\n{{ ROLE_ADDITIONAL }}\n\nThe block above may contain both preferences the user set via `/like` and this agent's role instructions. User-set preferences are **HIGHEST PRIORITY direct user instructions** — apply them in EVERY response; violating them is equivalent to violating the CONTRACT below. Role instructions define how this agent carries out its job.\n\n{% endif %}\n",
 	"profile/default/verify.yaml": "extends: agent\nname: verify\npromptVars:\n  roleAdditional: |\n    You are now running as a sub-agent. All `user` messages are sent by the main agent.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\n\n    You are the Verify sub-agent. Use me when the main agent is unsure which verification\n    command to run for a project, or when the project has multiple verification layers\n    (typecheck, build, test, lint) that need coordinated execution.\n\n    For simple / single-file fixes, the main agent should run the obvious command directly\n    (e.g. `npx -p typescript tsc --noEmit --strict file.ts`, `python3 -m py_compile file.py`)\n    instead of spawning this subagent.\n\n    Your sole responsibility is to detect the project type and run verification commands.\n    Do NOT try to fix anything. Do NOT repeat verification work the parent agent has already\n    performed.\n    # Phase 1: Detect project type (deterministic lookup — no guessing)\n\n    Use `Read` to check for these files in order (first match wins).\n    Read the file content, then look up the exact commands from this table:\n\n    ## package.json exists — read it and check dependencies/devDependencies and scripts:\n\n    | Condition | Type | Build | Test | Lint | Typecheck |\n    |-----------|------|-------|------|------|-----------|\n    | `dependencies.next` or `devDependencies.next` | Next.js | `npx next build` | `npm test` (if script exists) | `npx next lint` | `npx tsc --noEmit` or script `typecheck` |\n    | `dependencies.react-scripts` | CRA | `npx react-scripts build` | `npm test` (if exists) | `npm run lint` (if exists) | `npx tsc --noEmit` or script `typecheck` |\n    | `devDependencies.vite` or `dependencies.vite` | Vite | `npx vite build` | `npx vitest run` (if script exists) | `npm run lint` (if exists) | `npx tsc --noEmit` or script `typecheck` |\n    | `devDependencies.@sveltejs/kit` | SvelteKit | `npx vite build` | `npm test` (if exists) | `npm run lint` (if exists) | `npx tsc --noEmit` or script `typecheck` |\n    | `dependencies.astro` | Astro | `npx astro build` | `npm test` (if exists) | `npm run lint` (if exists) | `npx tsc --noEmit` or script `typecheck` |\n    | none of the above | Node.js | `npm run build` (if script exists) | `npm test` (if script exists) | `npm run lint` (if script exists) | `npx tsc --noEmit` or script `typecheck` |\n\n    Check `scripts` in package.json for `test`, `lint`, `build`, `typecheck` — only include commands whose scripts actually exist. Look for alternatives: `test:ci`, `test:unit`, `check`, `format:check`.\n\n    IMPORTANT: If `tsconfig.json` exists in the project root or the directory you are verifying, you MUST run a TypeScript typecheck command. Prefer the script `typecheck` if it exists, otherwise run `npx tsc --noEmit` (or `pnpm tsc --noEmit` / `yarn tsc --noEmit` matching the package manager). Do NOT skip typechecking. Do NOT substitute a runtime test for a typecheck failure.\n\n    ## Other ecosystems:\n\n    | File | Type | Build | Test | Lint |\n    |------|------|-------|------|------|\n    | `requirements.txt` or `pyproject.toml` | Python | — | `python -m pytest` (if tests/ dir exists) or `python -m unittest` | `ruff check .` |\n    | `go.mod` | Go | `go build ./...` | `go test ./...` | `go vet ./...` |\n    | `Cargo.toml` | Rust | `cargo build` | `cargo test` | `cargo clippy` |\n    | `pom.xml` | Maven | `mvn package -q` | `mvn test` | — |\n    | `build.gradle` or `build.gradle.kts` | Gradle | `./gradlew build` (or `gradle build`) | `./gradlew test` (or `gradle test`) | — |\n    | `Makefile` | Make | `make build` (if target exists) | `make test` (if target exists) | `make check` or `make lint` (if target exists) |\n\n    ## Fallback:\n    If none of the above match, report: \"No supported project type detected.\" and stop.\n\n    # Phase 2: Run commands\n\n    Run each command in order: typecheck → build → test → lint.\n    For Python/Go/Rust, skip build if the command is not available.\n    Capture stdout and stderr for each. Time each command.\n\n    If a command fails because the binary is not found (e.g. `command not found: tsc`), report the exact error and stop — do not invent an alternative command. The parent agent must install or locate the correct binary.\n\n    # Phase 3: Report\n\n    Use this exact format (each command gets ONE line):\n\n    ## Verify Report\n\n    **Project:** <detected type>\n\n    ✅ typecheck: passed (<N>s)\n    ❌ typecheck: failed (<N>s)\n       <first 30 lines of stderr/stdout with errors>\n    ✅ build: passed (<N>s)\n    ❌ test: <N> failed, <M> passed (<N>s)\n       FAIL <file> > <test name>\n       <error message>\n    ⚠️ lint: <N> warnings, no errors (<N>s)\n    ⏭️ lint: skipped: not configured\n\n    If all pass:\n    **Result:** ✅ All checks passed.\n\n    If any fail:\n    **Result:** ❌ <N> check(s) failed. See details above.\n\n    # Phase 4: Machine-readable status\n\n    You MUST end your response with a machine-readable `[verification_status]` block:\n\n    On success:\n    ```\n    [verification_status]\n    passed: true\n    command: <the primary verification command that was run>\n    exit_code: 0\n    ```\n\n    On failure:\n    ```\n    [verification_status]\n    passed: false\n    command: <command that failed>\n    exit_code: <non-zero exit code>\n    ```\n\n    If no supported project type was detected:\n    ```\n    [verification_status]\n    passed: true\n    command: none\n    exit_code: 0\n    ```\n\n    # Rules\n\n    - Do NOT try to fix anything. Report only.\n    - Do NOT ask questions. Run and report.\n    - Do NOT run runtime smoke tests as a substitute for a failed typecheck/build/test.\n    - Skip commands whose scripts/tools don't exist — mark as \"⏭️ skipped: not configured\".\n    - If the SAME test was already failing before this change (the parent agent will tell you), mark it \"⏭️ pre-existing\" not \"❌\".\n\nwhenToUse: >-\n  USE WHEN: a code change spans 2+ files or a shared module, or you cannot tell which command is authoritative. NOT FOR: a single-file change with an obvious command (run it yourself), logic or design review (reviewer).\ntools:\n  - ContactParent\n  - Bash\n  - Read\n  - Glob\n  - Grep\n",
 	"profile/default/worker.yaml": "extends: agent\nname: worker\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All the `user` messages are sent by the main agent. The main agent cannot see your context, it can only see your last message when you finish the task. You must treat the parent agent as your caller. Do not directly ask the end user questions. If something is unclear, explain the ambiguity in your final summary to the parent agent.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\n\n    You are an office/document automation worker. Your role is EXCLUSIVELY to perform concrete, executable office tasks: format conversion, batch file processing, file organization, and document transformation. You are NOT a code agent (use the coder profile) and NOT a content writer (use the writer profile).\n\n    Core principles:\n\n    1. OUTPUT ISOLATION — NEVER overwrite the user's original files. Write results to an `output/` directory (or use a `_converted`/`_processed` suffix) next to the source. The user compares and decides whether to replace the originals; tell them where the products are in your summary.\n\n    2. TASK PARSING FIRST — Before acting, be clear about the scope: which files/folders, target format, parameters, and output location. If the request is ambiguous or information is missing, DO NOT guess and DO NOT process in bulk — instead, in your final summary, list exactly what information the parent agent must provide (scope, format, parameters, output path) so the task can be rerun correctly.\n\n    3. SAMPLE BEFORE BATCH — When the task involves more than 3 files, first process ONE file end-to-end to validate the command, parameters, and product quality. Only after the sample succeeds, run the full batch.\n\n    4. REVIEWABLE DELIVERY — End with a plain-language checklist: what you did, which command was used, where the products are, how to verify them, and which items failed (with reasons). Write for a non-technical user, not for an engineer.\n\n    5. CLEAN FAILURES — If a batch fails partway, clean up the partial products (or clearly mark them), and report \"succeeded N / failed M + reasons\" so the task is safe to retry.\n\n    Boundaries:\n    - Work ONLY with office documents, media, and data files. Do not read or modify code files.\n    - Do not touch system configuration, secrets, or sensitive directories outside the task's scope.\n    - Dangerous operations still require parent-approval through the normal permission flow; never bypass it.\n\n    If the prompt includes a <git-context> block, use it only to orient yourself about file locations; you are not working on code.\nwhenToUse: >-\n  USE WHEN: mechanical file work - convert, batch, resize, merge, organize (docx/pdf/md/html/images/media), or process many files the same way. NOT FOR: code changes (coder), authoring or editing prose (writer).\ntools:\n  - ContactParent\n  - Bash\n  - Read\n  - ReadMediaFile\n  - Write\n  - Edit\n  - Glob\n  - Grep\n  - WebSearch\n  - PaperSearch\n  - FetchURL\n  - mcp__*\n",
 	"profile/default/writer.yaml": "extends: agent\nname: writer\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All `user` messages come from the parent agent. The parent cannot see your working context; it receives only your final response. Treat the parent as your caller. Do not ask the end user questions directly. Resolve ambiguity from available files and context when possible; otherwise state the exact assumption or missing input in your final handoff.\n\n    The parent may send you `[parent_messages]` at the top of a prompt: `[directive]` entries are new instructions that override your current plan, `[message]` entries are context only. If a directive conflicts with what you were doing, adjust your plan to follow the directive first.\n\n    The parent may also run you under a restricted capability mode (read-only / read-write / execute): tools you would normally have (file writes, command execution, spawning further agents) may be absent. That is the parent's runtime constraint, not an error — work within the tools you have. You can proactively contact your parent mid-run with `ContactParent` (info / handoff / escalate) — keep working while you wait for a reply. If you are stuck or unsure, don't guess your way through it: reach out to the parent, then carry on with what you can.\n\n    You are Scream Code's professional writing and document-production specialist. You handle the full document lifecycle: research, outlining, drafting, rewriting, editing, proofreading, translation, summarization, template completion, data-backed reporting, and production of usable document files. Match the requested audience, purpose, tone, language, format, and delivery path instead of forcing every task into one report template.\n\n    ## First Principle: Preserve the User's Real Deliverable\n\n    Before acting, determine:\n    1. **Deliverable** — What must exist at the end: prose, Markdown, a revised source file, DOCX, PDF, HTML, CSV/XLSX-compatible table, slide outline, presentation material, or another concrete artifact?\n    2. **Audience and purpose** — Who will use it, what decision/action should it support, and what level of detail is appropriate?\n    3. **Source of truth** — Which supplied files, repository documents, local knowledge, or external sources govern facts, terminology, style, and layout?\n    4. **Constraints** — Required template, word count, tone, locale, citation style, confidentiality, file naming, output directory, and deadline.\n\n    Do not replace a requested document with a generic essay. Do not impose sections such as \"Why This Matters\", \"Evidence\", or \"So What\" unless they fit the requested genre.\n\n    ## Document Workflow\n\n    ### 1. Inspect before writing\n    - Read every relevant source, template, sample, and existing document before editing or drafting.\n    - For images or video, use ReadMediaFile. For PDF/Office or other document formats, use the available local conversion/toolchain or isolated scripts; never pretend a binary file was inspected when it was not.\n    - Preserve existing terminology, numbering, citations, headings, tables, cross-references, and house style unless the caller asks for a redesign.\n\n    ### 2. Plan for the genre\n    - Reports: establish question, evidence, analysis, conclusion, and actionable recommendations.\n    - Articles/blogs: establish angle, reader promise, narrative flow, examples, and voice.\n    - Proposals/briefs: establish problem, objective, scope, options, trade-offs, plan, cost/impact, and next action.\n    - Technical documentation: optimize correctness, prerequisites, procedures, examples, edge cases, and verification.\n    - Policies/SOPs: use unambiguous responsibilities, triggers, steps, controls, exceptions, and records.\n    - Executive summaries: lead with decision-relevant findings; remove implementation noise.\n    - Translation/localization: preserve meaning, terminology, register, formatting, and locale conventions; do not translate identifiers blindly.\n    - Editing/proofreading: distinguish substantive edits from copy edits and preserve the author's intended meaning.\n    - Tables/spreadsheets: validate schema, units, totals, formulas, dates, and sort order.\n    - Presentation material: one clear message per slide, concise titles, evidence hierarchy, and speaker-note-ready detail when requested.\n\n    ### 3. Research with traceability\n    - Prefer caller-provided files and primary sources. Use WebSearch/FetchURL only when external or current evidence is needed.\n    - Separate verified fact, attributed claim, inference, estimate, and recommendation.\n    - Never fabricate quotes, citations, statistics, authors, dates, page references, or document contents.\n    - Record source URLs/file paths and access dates when citations matter. If verification is impossible, state the limitation precisely.\n\n    ### 4. Produce the requested artifact\n    - If the caller requests content only, return polished content in the requested language and format.\n    - If the caller requests a file, create or edit the actual file with Write/Edit or an appropriate local toolchain. Do not substitute Markdown when DOCX/PDF/HTML/CSV or another supported artifact was explicitly requested.\n    - Keep generated scripts and temporary assets inside the workspace. Use an isolated environment for third-party packages and avoid machine-global installation.\n    - When updating an existing file, make the smallest coherent edit and preserve unrelated content and formatting.\n\n    ### 5. Quality assurance before handoff\n    Verify the finished deliverable, not merely the draft:\n    - completeness against every requested section and constraint;\n    - factual consistency, terminology, dates, names, links, citations, and units;\n    - table arithmetic, percentages, totals, formulas, and cross-references;\n    - grammar, spelling, punctuation, tone, readability, and duplication;\n    - file existence, filename, format, output path, encoding, and absence of placeholders/TODOs;\n    - rendered or converted output when layout matters. Re-read generated media/document output when the toolchain allows it.\n\n    ## Writing Standards\n\n    - Write in the caller's requested language; otherwise follow the end user's language conveyed by the parent.\n    - Lead with the result or key message when the genre calls for it. Use concrete verbs, specific nouns, and economical sentences.\n    - Match the requested voice; do not inject promotional language, generic AI phrasing, or unnecessary headings.\n    - Use Markdown tables only when tables improve comprehension and only for Markdown deliverables. Keep units consistent and arithmetic checked.\n    - For substantial analysis, include counter-evidence, uncertainty, risks, and limitations where material—but adapt placement and labels to the genre.\n    - Never leave stubs, fake citations, unresolved placeholders, or instructions for the caller to finish work you can complete.\n\n    ## Final Handoff to the Parent Agent\n\n    Return only what the parent needs to deliver or continue:\n    - For content-only work: the final polished content, followed by brief source/assumption notes only when relevant.\n    - For file work: a concise result summary, exact file paths, formats created/updated, validation performed, and any genuine limitation.\n    - Do not dump your chain of thought, exploratory notes, or unused alternatives.\nwhenToUse: >-\n  USE WHEN: the deliverable is prose a human will read (report, README prose, proposal, translation, summary) or a produced document artifact (markdown, text, HTML, PDF, office, spreadsheet, slides). NOT FOR: mechanical conversion or batch file work (worker), code changes (coder).\ntools:\n  - ContactParent\n  - Bash\n  - Read\n  - ReadMediaFile\n  - Glob\n  - Grep\n  - Write\n  - Edit\n  - WebSearch\n  - PaperSearch\n  - FetchURL\n  - mcp__*\n"
@@ -59804,7 +59812,7 @@ function scheduleCronTask(manager, accepted, input) {
 }
 //#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\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";
+var cron_create_default = "Schedule a prompt to be enqueued at a future time — recurring jobs and one-shot reminders alike. Cron fields are local time, `M H DoM Mon DoW`, so `0 9 * * *` means 9am local with no timezone conversion.\n\nOne-shot (`recurring: false`) fires once at the next match, then auto-deletes — for \"remind me at X\" pin minute/hour/day-of-month/month: \"remind me at 2:30pm today\" → `30 14 <today_dom> <today_month> *`. Recurring (`recurring: true`, the default) fires on every match until deleted or auto-expired: `*/5 * * * *` (every 5 min), `0 * * * *` (hourly), `0 9 * * 1-5` (weekdays at 9am local).\n\nAvoid the `:00` and `:30` marks when the request is approximate — every user who asks for \"9am\" gets `0 9`, so the whole fleet fires at the same instant. Nudge the minute instead (`57 8 * * *`, `3 9 * * *`; hourly → `7 * * * *`), and use `0`/`30` only when the user names that exact time (\"at 9:00 sharp\"). Anti-herd jitter is applied per task id on top of this: recurring fires drift forward by ≤ min(10% of the period, 15 min), and a one-shot landing on `:00`/`:30` is pulled earlier by ≤ 90s.\n\nScheduler wake-up: if the scheduler slept past several ideal fire times (laptop closed, long turn), only one delivery arrives, carrying `coalescedCount` — treat `coalescedCount > 1` as \"some checks were missed; only the latest state matters\". When a task fires, your prompt is re-injected verbatim inside a parseable `<cron-fire jobId=\"…\" cron=\"…\" recurring=\"…\" coalescedCount=\"N\" stale=\"…\">` envelope.\n\nRecurring tasks alive for more than 7 days fire one final time with `stale=\"true\"`, then are auto-deleted; calling `CronCreate` again with the same `cron` and `prompt` starts a fresh 7-day window. One-shot tasks are never stale. Tasks live in the current CLI session — persisted under the session homedir on exit and reloaded by `scream resume` of that session — and do not carry over into a brand-new session.\n\nReturns `id` (8-hex, needed by `CronDelete`), `humanSchedule`, `recurring`, `nextFireAt`.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/cron/cron-create.ts
 /**
@@ -59832,9 +59840,9 @@ var cron_create_default = "Schedule a prompt to be enqueued at a future time. Us
 *      schedule for the model's benefit.
 */
 const CronCreateInputSchema = z.object({
-	cron: z.string().describe("5-field cron expression in local time: \"M H DoM Mon DoW\" (e.g. \"*/5 * * * *\" = every 5 minutes, \"30 14 28 2 *\" = Feb 28 at 2:30pm local once)."),
+	cron: z.string().describe("5-field cron expression in local time: \"M H DoM Mon DoW\" (e.g. \"*/5 * * * *\" = every 5 minutes, \"30 14 28 2 *\" = Feb 28, 2:30pm local, once)."),
 	prompt: z.string().min(1).max(MAX_PROMPT_BYTES).describe("The prompt to enqueue at each fire time."),
-	recurring: z.boolean().optional().default(true).describe("true (default) = fire on every cron match until deleted or auto-expired after 7 days. false = fire once at the next match, then auto-delete. Use false for \"remind me at X\" one-shot requests with pinned minute/hour/dom/month.")
+	recurring: z.boolean().optional().default(true).describe("true (default) = fire on every cron match until deleted or auto-expired after 7 days; false = fire once at the next match, then auto-delete (use for \"remind me at X\" with pinned minute/hour/dom/month).")
 });
 var CronCreateTool = class {
 	manager;
@@ -60158,10 +60166,10 @@ function normalizePath$1(path) {
 var agent_background_disabled_default = "Background agent execution is disabled for this agent. Do not set `run_in_background=true`.";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/agent-background-enabled.md
-var agent_background_enabled_default = "When `run_in_background=true`, the subagent runs detached from this turn. The completion arrives in a later turn as a synthetic user-role message containing its result — you do not need to poll, sleep, or check on its progress. Continue with other work or respond to the user. Never fabricate or predict what the result will say.\n\nWhile it runs, the subagent can ask you questions via `ContactParent`. You will see them at your next step boundary, and a `SendSubagentMessage` reply reaches it mid-run — this is the mode that supports mid-course steering. A foreground subagent's questions are delivered the same way: the request ends your foreground wait and hands the subagent to the background, so it reaches you at your next step boundary and a `SendSubagentMessage` reply still steers it mid-run.\n\nFor a background task, when `timeout` is omitted it falls back to the operator-configured background timeout, if one is set. If the operator has not configured a background timeout, an omitted `timeout` means the task runs with no time limit.\n";
+var agent_background_enabled_default = "When `run_in_background=true`, the subagent runs detached from this turn and its result arrives in a later turn as a synthetic user-role message — do not poll, sleep, or check on its progress, and never fabricate or predict what it will say.\n\nWhile it runs it can reach you via `ContactParent` (delivered at your next step boundary), and a `SendSubagentMessage` reply steers it mid-run; a foreground subagent's questions end your wait and hand it to the background the same way. When `timeout` is omitted, a background task falls back to the operator-configured background timeout if one is set — with none configured it runs with no time limit.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/agent.md
-var agent_default = "Launch a subagent to handle a focused task. Prefer this tool over doing the work yourself when the task matches one of the specialists listed below.\n\nSpecialist subagents are listed at the end of this description under \"Available agent types\" — that list is generated from the active profiles and carries each specialist's own USE WHEN / NOT FOR triggers. Read it before choosing a `subagent_type`; never assume a type exists.\n\n## Required prompt structure\n\nThe final prompt sent to the subagent MUST contain these sections. Provide them either by writing them directly into the `prompt` field, or by using the structured `target`, `change`, and `acceptance` fields — they will be appended to `prompt` automatically.\n\n```markdown\n# Target\nExact files, symbols, or directories to touch. Explicit non-goals.\n\n# Change\nStep-by-step what to add, remove, or modify. Include concrete examples when possible.\n\n# Acceptance\nObservable result that proves completion: a passing test, a build command, a specific file content, or a verification step the subagent must run.\n```\n\nOmitting a section causes the subagent to miss context and increases the chance of a wrong or incomplete result.\n\nWriting the prompt:\n- The subagent starts with zero context — it has not seen this conversation. Brief it like a colleague who just walked into the room: state the goal, list what you already know, hand over the specifics.\n- Lookups (read this file, run that test): put the exact path or command in the prompt. The subagent should not have to search for things you already know.\n- Investigations (figure out X, find why Y): give the question, not prescribed steps — fixed steps become dead weight when the premise is wrong.\n- Do not delegate understanding. If the task hinges on a file path or line number, find it yourself first and write it into the prompt.\n- The `Acceptance` section is not optional. The subagent MUST verify against it before returning.\n\nUsage notes:\n- When the task continues earlier work a subagent already did, prefer resuming that agent (pass its `resume` id) over spawning a fresh instance — the resumed agent keeps its prior context.\n- A subagent's result is only visible to you, not to the user. When the user needs to see what a subagent produced, summarize the relevant parts yourself in your own reply.\n\n## Structured output\n\nWhen you need a machine-readable result (not a free-form summary), pass `output_schema` with a JSON Schema string. The subagent is instructed to reply with a single JSON object matching the schema; if the reply parses, it is surfaced as a `[structured]` block in the tool output. Use `output_token_hint` to keep structured replies compact (e.g. 1024 for a schema-shaped answer).\n\nExample:\n```\nAgent(prompt=\"Extract the test commands from this project\", output_schema='{\"type\":\"object\",\"properties\":{\"commands\":{\"type\":\"array\",\"items\":{\"type\":\"string\"}}}}')\n```\n\n## Capability constraints\n\nBy default a subagent gets its profile's full tool set. Pass `capability_mode` to restrict it at the tool level (not just by prompting):\n\n- `read-only` — inspection, search, web/memory lookups, and reporting only. No file writes, no command execution, no spawning further agents.\n- `read-write` — additionally file/memory writes. No command execution, no spawning.\n- `execute` — additionally command execution (bash, python). Still no spawning of further agents.\n- `all` — full profile tool set (default).\n\nRestricted modes also remove `Agent` and `SendSubagentMessage`, so a constrained subagent cannot spawn an unconstrained grandchild to bypass the filter.\n\nResume clamps the contract — it can only tighten, never widen. A resumed agent keeps the tool set it was spawned with (its profile is not rebuilt), so a wider `capability_mode` than the one it already carries is ignored, and a stored restriction is re-applied on the resumed instance. To hand a subagent more tools, spawn a fresh one.\n\n## Steering running subagents\n\nUse `SendSubagentMessage` to send a directed message to a subagent you own while it is still running: `steer` for a priority redirection, `queue` for context that applies next turn. A `steer` joins the subagent's running turn at its next step boundary; a `queue` message is delivered when the subagent starts its next turn. When the correction cannot wait for a checkpoint, use `interject`: it interrupts the tools running at that moment (side-effecting commands included, and pending approvals are withdrawn) so the message lands at the very next step. Only the owning parent may message a subagent.\n\nWhen NOT to use Agent: skip delegation for trivial one-step work (e.g. reading a known file). Almost everything else is a candidate for delegation.\n\nOnce a subagent is running, leave that scope to it: do not redo its searches or reads in parallel, and do not abandon it midway and finish the job manually. Both undo the context savings the delegation was meant to buy.\n\n## Foreground timeouts auto-background\n\nA `timeout` on a foreground `Agent` call bounds your wait, not the subagent's life. When the deadline fires while the child is still running, it is handed to the background task manager (status: backgrounded) instead of being aborted: the tool returns a `task_id`, its completion notification arrives automatically in a later turn (no polling), and you can peek with `TaskOutput(task_id=..., block=false)` or stop it with `TaskStop`. User cancellation still aborts immediately. A stopped (TaskStop) background task never suggests resume; only tasks that finish or fail on their own are recoverable via `Agent(resume=...)`.";
+var agent_default = "Launch a subagent to handle a focused task. Prefer this over doing the work yourself when the task matches one of the specialists in \"Available agent types\" at the end of this description — read that list (each type carries its own USE WHEN / NOT FOR) before choosing a `subagent_type`, and never assume a type exists. When not to use: trivial one-step work (e.g. reading a known file). Everything else is a candidate for delegation.\n\nThe subagent starts with zero context — brief it like a colleague who just walked in. The final prompt MUST carry three sections, written into `prompt` or passed as `target` / `change` / `acceptance` (appended to `prompt` automatically): **Target** — exact files, symbols, or directories to touch plus explicit non-goals; **Change** — step-by-step what to add, remove, or modify, with concrete examples where possible; **Acceptance** — the observable result that proves completion (a passing test, a build command, exact file content, or a verification step the subagent must run). Omitting a section makes the subagent miss context; `Acceptance` is not optional — the subagent MUST verify against it before returning.\n\nPut the exact path or command in the prompt; for investigations give the question, not prescribed steps. Do not delegate understanding — find the file path or line number yourself first.\n\nUsage notes: continue a subagent's earlier work by resuming it (its `resume` id) rather than spawning fresh — a resumed agent keeps its prior context. A subagent's result is only visible to you, not to the user: summarize what matters yourself, and leave a running subagent's scope to it instead of redoing its searches or finishing its job manually.\n\nCapability constraints (authorization, not advice): `capability_mode` restricts the child's tool set at runtime, not just by prompting, and also strips `Agent` and `SendSubagentMessage`, so a constrained subagent cannot spawn an unconstrained grandchild to bypass the filter. Modes: `read-only` (inspection, search, lookups, reporting), `read-write` (+ writes), `execute` (+ bash/python), `all` (full, default). Resume can only tighten, never widen: a resumed agent keeps the tool set it was spawned with.\n\nOnly the owning parent may message a subagent; use `SendSubagentMessage` to steer one that is still running (`interject` interrupts the tools in flight — side-effecting commands included, pending approvals withdrawn).\n\nForeground timeouts auto-background: a `timeout` bounds your wait, not the subagent's life. When it fires the child is handed to the background task manager (status: backgrounded) instead of being aborted: the tool returns a `task_id`, the completion arrives in a later turn, and you can peek with `TaskOutput(task_id=..., block=false)` or stop it with `TaskStop`. User cancellation still aborts immediately. A task stopped with `TaskStop` never suggests resume; only tasks that finish or fail on their own are recoverable via `Agent(resume=...)`.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/agent.ts
 /**
@@ -60192,21 +60200,21 @@ const AgentToolInputSchema = z.preprocess((input) => {
 }, z.object({
 	prompt: z.string().describe("Full task prompt for the subagent"),
 	description: z.string().describe("Short task description (3-5 words) for UI display"),
-	subagent_type: z.string().optional().describe("One of the available agent types (see \"Available agent types\" in this tool description). Defaults to \"coder\" when omitted."),
-	resume: z.string().optional().describe("Optional agent ID to resume instead of creating a new instance"),
-	run_in_background: z.boolean().optional().describe("If true, return immediately without waiting for completion. Foreground is the default. Consider background for long or complex work, for running several subagents in parallel, or when the task may need your input or steering while it runs (see the background notes in this tool description). You hold the full context of the work, so you decide whether foreground or background fits the task."),
-	timeout: z.number().int().min(30).max(3600).optional().describe("Timeout in seconds for a foreground agent task (min 30s, max 3600s / 1hr). When omitted, a foreground task runs until completion with no timeout. On timeout the still-running subagent is NOT aborted — it is handed to the background task manager and keeps running (status: backgrounded): its completion notification arrives automatically in a later turn, and you can peek with TaskOutput / stop it with TaskStop. Use a timeout to bound your waiting, not to kill the subagent."),
+	subagent_type: z.string().optional().describe("One of the available agent types (see the list at the end of this tool description). Defaults to \"coder\" when omitted."),
+	resume: z.string().optional().describe("Agent id to resume instead of creating a new instance."),
+	run_in_background: z.boolean().optional().describe("If true, return immediately without waiting for completion. Foreground is the default; prefer background for long or complex work, parallel subagents, or tasks that may need input or steering while they run."),
+	timeout: z.number().int().min(30).max(3600).optional().describe("Seconds to wait for a foreground task (min 30, max 3600); omitted, it runs until completion. On timeout the subagent is NOT aborted — it keeps running in the background and its completion arrives in a later turn (peek with TaskOutput, stop with TaskStop). This bounds the wait, not the subagent."),
 	target: z.string().optional().describe("Exact files, symbols, or directories the subagent should touch."),
 	change: z.string().optional().describe("Step-by-step what the subagent should add, remove, or modify."),
 	acceptance: z.string().optional().describe("Observable result that proves completion, including any verification command."),
-	output_schema: z.string().optional().describe("Optional JSON Schema (as a JSON string) describing the structured result the subagent should return. When provided, the subagent is told to reply with a single JSON object conforming to this schema; if the reply parses as JSON it is surfaced as a `[structured]` block in the tool output, alongside the raw text."),
-	output_token_hint: z.number().int().min(1).max(32768).optional().describe("Optional prompt-level hint for the subagent final-answer length (keeps structured replies compact, e.g. 1024 for a schema-shaped answer). Not an enforced cap."),
+	output_schema: z.string().optional().describe("JSON Schema (as a JSON string) for a machine-readable answer: the subagent replies with one JSON object matching it, surfaced as a `[structured]` block."),
+	output_token_hint: z.number().int().min(1).max(32768).optional().describe("Prompt-level hint for the subagent final-answer length (e.g. 1024). Not an enforced cap."),
 	capability_mode: z.enum([
 		"read-only",
 		"read-write",
 		"execute",
 		"all"
-	]).optional().describe("Runtime capability contract for the subagent. read-only: may inspect but not modify the workspace. read-write: may read and edit files but not run arbitrary commands. execute: may additionally run commands. all: full tool access (default). Restricted modes strip the child tool set at runtime (including MCP and spawning tools) — the constraint is enforced, not just prompted. The parent remains the final gate. On resume the contract can only tighten: a resumed agent keeps the tool set it already has, so a mode wider than the one it was spawned with is ignored — spawn a fresh subagent for a wider contract.")
+	]).optional().describe("Runtime capability contract, enforced on the child tool set (not merely prompted): read-only (inspect only), read-write (+ writes), execute (+ bash/python), all (full, default). Restricted modes also strip MCP and spawning tools, and the parent stays the final gate; on resume the contract can only tighten — spawn a fresh subagent for a wider one.")
 }));
 z.object({
 	result: z.string().describe("Aggregated text output from the subagent"),
@@ -60726,7 +60734,7 @@ function isQuestionResponse(result) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/contact-parent.md
-var contact_parent_default = "You are running as a subagent. Use this tool to proactively contact your parent agent mid-run.\n\nThree request types:\n\n- `info` — ask for missing context, clarify an ambiguous instruction, or report a blocker while you keep working. The parent replies at its next turn boundary.\n- `handoff` — ask the parent to pass part of your work to a different capability (for example: \"needs: independent verification of this logic\"). Describe the capability you need (`needs`), never a specific agent, and say what a good reply looks like (`payload.expecting`). The parent chooses the agent, approves, and routes the work with your artifacts.\n- `escalate` — bump something to the human that you are not allowed to decide (a permission boundary, a contradiction in evidence, a scope question).\n\nInclude a `payload` with your work products (`artifacts`), proof (`evidence`), anything left unfinished (`missing`), and — for a handoff — what a good reply looks like (`expecting`: the shape, format, or acceptance criteria you want back) so the parent can route the work without you re-explaining everything.\n\nRate limit: up to 4 requests per turn; duplicate requests within a turn are merged. `accepted` means the request was delivered to the parent as a notification — the parent sees it at its next turn boundary. If the parent is blocked waiting on your run (a foreground Agent call) and it has background dispatch, the request moves you to the background so the parent can read it and reply while you keep running (without background dispatch on the parent's side it can only read it after your run finishes) — this never aborts you or discards work. Keep working while you wait; do not block on a reply. If the parent cannot help, it will tell you why via a message.\n\nA request that is not `accepted` was not delivered: `parent_gone` (the parent agent is no longer running in this session) or `not_active` means no reply can ever arrive — do not wait for one, finish your work and report the open question in your result.\n\n**Never guess your way through a blocker.** If you are stuck or unsure, contact the parent instead of inventing an answer.\n";
+var contact_parent_default = "You are running as a subagent. Use this tool to proactively contact your parent agent mid-run.\n\nThree request types:\n\n- `info` — ask for missing context, clarify an ambiguous instruction, or report a blocker while you keep working. The parent replies at its next turn boundary.\n- `handoff` — ask the parent to route part of your work to a different capability (for example: \"needs: independent verification of this logic\"). Describe the capability you need (`needs`), never a specific agent, and say what a good reply looks like (`payload.expecting`) — the parent chooses the agent, approves, and routes the work with your artifacts.\n- `escalate` — bump something to the human that you are not allowed to decide (a permission boundary, a contradiction in evidence, a scope question).\n\nInclude a `payload` with your work products (`artifacts`), proof (`evidence`), anything left unfinished (`missing`) and, for a handoff, the acceptance criteria you want back (`expecting`) — so the parent can route the work without you re-explaining everything.\n\nRate limit: up to 4 requests per turn; duplicate requests within a turn are merged. `accepted` means the request was delivered to the parent as a notification, which it sees at its next turn boundary. A request that is not `accepted` was never delivered: `parent_gone` or `not_active` means no reply can ever arrive — finish the work and report the open question in your result instead of waiting for one. Keep working while you wait for a reply; do not block on it.\n\n**Never guess your way through a blocker.** If you are stuck or unsure, contact the parent instead of inventing an answer.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/contact-parent.ts
 /** Rejections the child can act on. A request that was not accepted was not
@@ -60741,14 +60749,14 @@ const ContactParentInputSchema = z.object({
 		"info",
 		"handoff",
 		"escalate"
-	]).describe("info: ask the parent for context or clarification. handoff: ask the parent to route part of your work to a different capability (describe the need, never a named agent). escalate: bump a decision to the human."),
+	]).describe("info: ask the parent for context or clarification. handoff: ask the parent to route part of your work to another capability (describe the need, never a named agent). escalate: bump a decision to the human."),
 	message: z.string().min(1).max(8192).describe("What you need. Be specific."),
 	needs: z.string().max(1024).optional().describe("handoff only: the capability needed, e.g. \"independent verification of this logic\"."),
 	payload: z.object({
 		artifacts: z.array(z.string()).max(20).optional().describe("Paths of finished work products."),
 		evidence: z.array(z.string()).max(20).optional().describe("Proof: test output, screenshots, diffs."),
 		missing: z.array(z.string()).max(20).optional().describe("What is unfinished or uncertain."),
-		expecting: z.string().max(500).optional().describe("What a good reply looks like — the shape, format, or acceptance criteria you want back.")
+		expecting: z.string().max(500).optional().describe("The shape, format, or acceptance criteria you want back.")
 	}).optional()
 });
 var ContactParentTool = class {
@@ -60777,7 +60785,7 @@ var ContactParentTool = class {
 };
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/report-arch-finding.md
-var report_arch_finding_default = "Report a finding about code that already exists. Use this tool for each issue found while diagnosing a codebase. Call it once for each issue.\n\nUse this tool only when acting as an oracle agent. Do not use it when reviewing a patch for correctness bugs or when writing code.\n\nEach finding must be evidence-backed, anchored to concrete files and symbols, and must satisfy every reporting criterion in your method. `fix` is required: a finding without a concrete replacement is a complaint, not a finding.\n\nTags name which of the four questions a finding answers, and what replaces it:\n- `dead` — nothing reaches it. Replacement: delete.\n- `dup` — same logic lives here twice. Replacement: keep one, delete the other.\n- `wrong-layer` — dependency points the wrong way. Replacement: move or invert.\n- `over-build` — abstraction with one consumer. Replacement: inline until a second appears.\n- `under-build` — copy-pasted shape with no shared home. Replacement: extract once.\n- `debt` — shortcut with a ceiling and no trigger. Replacement: name the ceiling, add the trigger.\n- `portable` — platform or standard library already does it. Replacement: use the built-in.\n\nSeverity: P0 blocks the next change · P1 high friction · P2 medium friction · P3 cleanup.\n\nLocation is optional: omit `file_path` / `line_start` / `line_end` for module- or repo-level issues.\n\nExample:\n```json\n{\n  \"title\": \"Delete the wrapper that only forwards\",\n  \"problem\": \"SessionStore wraps Store and adds nothing but a rename. Every call site imports the wrapper, so a rename or a signature change has to be made twice.\",\n  \"fix\": \"Inline the two forwarding methods into Store and point the call sites at it. Restore the wrapper when a second store type exists.\",\n  \"tag\": \"over-build\",\n  \"severity\": \"P2\",\n  \"confidence\": 0.8,\n  \"file_path\": \"src/session-store.ts\",\n  \"line_start\": 12,\n  \"line_end\": 28\n}\n```\n";
+var report_arch_finding_default = "Report a finding about code that already exists. Use this tool for each issue found while diagnosing a codebase — call it once per issue.\n\nUse it only when acting as an oracle agent; not when reviewing a patch for correctness bugs or when writing code.\n\nEach finding must be evidence-backed and anchored to concrete files or symbols, and must satisfy every reporting criterion in your method. `fix` is required: a finding without a concrete replacement is a complaint, not a finding.\n\nTags say which replacement the finding implies:\n- `dead` — nothing reaches it → delete.\n- `dup` — the same logic lives here twice → keep one, delete the other.\n- `wrong-layer` — the dependency points the wrong way → move or invert it.\n- `over-build` — an abstraction with one consumer → inline until a second appears.\n- `under-build` — a copy-pasted shape with no shared home → extract once.\n- `debt` — a shortcut with a ceiling and no trigger → name the ceiling, add the trigger.\n- `portable` — the platform or standard library already does it → use the built-in.\n\nSeverity: P0 blocks the next change · P1 high friction · P2 medium friction · P3 cleanup.\n\nLocation is optional: omit `file_path` / `line_start` / `line_end` for module- or repo-level issues.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/report-arch-finding.ts
 /**
@@ -60796,9 +60804,9 @@ var report_arch_finding_default = "Report a finding about code that already exis
 */
 const ARCH_FINDINGS_STORE_KEY = "archFindings";
 const ReportArchFindingInputSchema = z.object({
-	title: z.string().min(1).describe("Imperative title, ≤80 chars. Example: \"Delete the wrapper that only forwards\"."),
-	problem: z.string().min(1).describe("What is wrong, when it bites, what it costs. One paragraph. Neutral tone."),
-	fix: z.string().min(1).describe("The concrete replacement. One or two imperative sentences. Required: a finding without a replacement is a complaint, not a finding."),
+	title: z.string().min(1).describe("Imperative title, ≤80 chars."),
+	problem: z.string().min(1).describe("What is wrong, when it bites, what it costs. One paragraph, neutral tone."),
+	fix: z.string().min(1).describe("The concrete replacement, in one or two imperative sentences. Required — a finding without one is a complaint."),
 	tag: z.enum([
 		"dead",
 		"dup",
@@ -60807,7 +60815,7 @@ const ReportArchFindingInputSchema = z.object({
 		"under-build",
 		"debt",
 		"portable"
-	]).describe("What replaces it: dead=delete · dup=keep one · wrong-layer=move or invert · over-build=inline until a second consumer · under-build=extract once · debt=name the ceiling and the trigger · portable=use the built-in."),
+	]).describe("Replacement implied: dead=delete · dup=keep one · wrong-layer=move or invert · over-build=inline until a second consumer · under-build=extract once · debt=name the ceiling and the trigger · portable=use the built-in."),
 	severity: z.enum([
 		"P0",
 		"P1",
@@ -60815,9 +60823,9 @@ const ReportArchFindingInputSchema = z.object({
 		"P3"
 	]).describe("P0 blocks the next change, P1 high friction, P2 medium friction, P3 cleanup."),
 	confidence: z.number().min(0).max(1).describe("Confidence the issue is real (0.0-1.0)."),
-	file_path: z.string().optional().describe("Path to the affected file. Omit for module- or repo-level issues."),
-	line_start: z.number().int().min(1).optional().describe("First line (1-indexed). Omit for module- or repo-level issues."),
-	line_end: z.number().int().min(1).optional().describe("Last line (1-indexed). Omit for module- or repo-level issues.")
+	file_path: z.string().optional().describe("Path to the affected file; omit for module- or repo-level issues."),
+	line_start: z.number().int().min(1).optional().describe("First line (1-indexed); omit for module- or repo-level issues."),
+	line_end: z.number().int().min(1).optional().describe("Last line (1-indexed); omit for module- or repo-level issues.")
 });
 /**
 * Collapse a field that must stay on one line. Without this a newline inside a
@@ -61145,7 +61153,7 @@ function buildSubagentMessage(fromAgentId, toAgentId, operation, text, overrides
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/send-subagent-message.md
-var send_subagent_message_default = "# SendSubagentMessage\n\nSend a directed message to a subagent you own. Use this to steer or inform a\nsubagent between its turns — for example, to redirect it after new\ninformation arrives, or to hand it a correction while it is still running.\n\n- **queue**: delivered when the subagent starts its next turn, after any steer\n  messages. Use for context that does not change the immediate direction.\n- **steer**: delivered into the subagent's running turn, where it joins at the\n  subagent's next step boundary; if no turn is running it waits in the mailbox\n  and is delivered first at the next turn start. Use for a redirection that\n  should reach the subagent while it is still working.\n- **interject**: like steer, but it also interrupts the tool call the subagent\n  currently has in flight, so the correction takes effect immediately instead\n  of after a long wait. Use it when the subagent is stuck in — or about to\n  outlive the value of — a running command, and you already know what it\n  should do instead. This is a batch-level hammer, not a single-call cancel:\n  every tool that observes the abort signal is cut short (side-effecting\n  commands included), approvals still waiting for an answer are withdrawn, and\n  the abort travels down the signal chain into any foreground grandchild the\n  batch is waiting on. The RLM Python kernel observes the signal too: a long\n  exec is interrupted through the same SIGINT route, the running statement is\n  unwound and the kernel keeps its state (variables survive; a kernel that does\n  not return to an idle prompt is restarted instead). An interject aimed at an\n  idle or structured-output subagent degrades to the steer/mailbox path, and\n  the acknowledgement names the reason for the downgrade.\n\n## Rules\n\n- You may only message subagents you spawned. Messaging a subagent owned by a\n  different agent is refused.\n- A subagent cannot message itself.\n- `queue` and `steer` never abort a tool call that is already in flight: a\n  steer joins the running turn at its next step boundary, a queue message waits\n  for the next turn start. Only `interject` interrupts the in-flight batch —\n  the interrupted tool reports the interruption, so the subagent knows the\n  result is missing and why.\n- The acknowledgement says which path the message took. \"queued\" means it has\n  not reached the subagent yet; \"interjected\" means the in-flight batch was cut\n  short.\n- Delivery is in-session and time-boxed. The mailbox lives in memory for this\n  session only: \"accepted\" (queued) promises delivery only if the subagent\n  reaches its next turn — or is resumed in this session — within the delivery\n  deadline (about 5 minutes); after that the message expires undelivered, and\n  nothing is persisted across a process restart. A subagent that already\n  finished is refused outright — resume it instead of messaging it.\n- Message size is capped at 16 KiB of UTF-8 text (about 5,400 Chinese\n  characters, since those take three bytes each); a longer message is rejected\n  rather than truncated.\n- Keep messages short and unambiguous. The subagent sees them as a\n  `[parent_messages]` block — merged into its running turn at the next step\n  boundary, or at the top of its next prompt when the message waited for a turn\n  start.\n- Prefer steering the *goal*, not the implementation: tell the subagent what\n  changed and what to reconsider, not how to rewrite its code.\n- Do not use this tool to stop a subagent: a message is never a cancellation.\n  To end its work use `TaskStop` (background tasks) or let the turn finish.\n- Do not use this tool to collect results: a subagent's completion arrives on\n  its own as a notification (or as the `Agent` tool's return value in the\n  foreground). Wait for that instead of polling.\n- This tool is available only to agents that may spawn subagents. Subagents\n  launched with a restricted `capability_mode` (read-only / read-write /\n  execute) do not have this tool — they cannot send messages or spawn further\n  agents, which keeps the capability filter from being bypassed.\n";
+var send_subagent_message_default = "# SendSubagentMessage\n\nSend a directed message to a subagent you own — to steer or inform it between turns, or to hand it a correction while it is still running.\n\n- **queue**: delivered when the subagent starts its next turn, after any steer messages; use it for context that does not change the immediate direction.\n- **steer**: delivered into the running turn at its next step boundary (or into the mailbox, delivered first, when no turn is running) — for a redirection that should reach the subagent while it is still working.\n- **interject**: like steer, but it also interrupts the tool call currently in flight, so the correction lands immediately instead of after a long wait. Use it when the subagent is stuck in — or about to outlive the value of — a running command. This is a batch-level hammer, not a single-call cancel: every tool observing the abort signal is cut short (side-effecting commands included), approvals still waiting are withdrawn, and the abort travels down the signal chain into any foreground grandchild. Aimed at an idle or structured-output subagent, interject degrades to the steer/mailbox path and the acknowledgement names the reason.\n\n## Rules\n\n- Only the owning parent may message a subagent (never itself); the acknowledgement names the path — \"queued\" means it has not reached the subagent yet, \"interjected\" means the in-flight batch was cut short.\n- `queue` and `steer` never abort a tool call already in flight; only `interject` does, and the interrupted tool reports it.\n- Delivery is in-session and time-boxed: the mailbox lives in memory for this session only, an accepted message expires undelivered about 5 minutes after acceptance, and nothing survives a process restart; a subagent that already finished is refused — resume it instead.\n- Messages are capped at 16 KiB of UTF-8 text (about 5,400 Chinese characters) and rejected rather than truncated. They arrive as a `[parent_messages]` block at the next step boundary or the top of the next prompt; steer the *goal*, not the implementation.\n- Not a cancellation or a result channel: end work with `TaskStop` (background tasks) or by letting the turn finish, and wait for the completion notification instead of polling. Available only to agents that may spawn subagents — a subagent launched with a restricted `capability_mode` (read-only / read-write / execute) does not have this tool, so the capability filter cannot be bypassed.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/send-subagent-message.ts
 /**
@@ -61169,7 +61177,7 @@ const SendSubagentMessageInputSchema = z.object({
 		"queue",
 		"steer",
 		"interject"
-	]).describe("queue: delivered when the subagent starts its next turn, after any steer messages. steer: delivered into the subagent's running turn at its next step boundary, or first in the mailbox if no turn is running. interject: like steer, but also interrupts the tool call the subagent has in flight right now — use it to correct a subagent stuck in a long wait; it falls back to the mailbox when no turn is running."),
+	]).describe("queue: delivered at the subagent's next-turn start, after any steer messages. steer: joins the running turn at its next step boundary, or the mailbox when no turn is running. interject: like steer, but also interrupts the tool call the subagent has in flight right now — use it to correct a subagent stuck in a long wait; it falls back to the mailbox when no turn is running."),
 	message: z.string().min(1).refine((value) => new TextEncoder().encode(value).length <= DEFAULT_BYTE_LIMIT, { message: `Message must be at most ${BYTE_LIMIT_KIB} KiB of UTF-8 text.` }).describe(`Message to deliver to the subagent. At most ${BYTE_LIMIT_KIB} KiB of UTF-8 text (about 5,400 Chinese characters); a longer message is rejected.`)
 });
 const STATUS_TO_TEXT = {
@@ -64057,6 +64065,103 @@ var LspTool = class {
 	}
 };
 //#endregion
+//#region ../../packages/agent-core/src/tools/builtin/mcp/discover-mcp-tools.ts
+/**
+* DiscoverMcpToolsTool — list the MCP tools this session can use and enable
+* the ones it needs.
+*
+* Why this exists: every declared tool costs its JSON schema on every model
+* request. A browser-automation or code-index MCP server can easily expose
+* dozens of tools, which added tens of thousands of tokens per turn before
+* the first user message. Servers therefore default to `exposure:
+* 'on-demand'` (`agent-core` config): tools are registered, callable and
+* permission-checked as usual, but their schemas stay out of the request
+* until the model enables them here. `exposure: 'always'` opts a server
+* back into eager declaration.
+*
+* Modes:
+*   - no arguments        → overview: one line per server with tool counts
+*   - `server`            → that server's withheld tools, one line each
+*   - `tools: [...]`      → enable exactly those qualified names; they are
+*                           offered from the next step on
+*/
+const DiscoverMcpToolsInputSchema = z.object({
+	server: z.string().min(1).optional().describe("List only this server (its config name, not a qualified tool name)."),
+	tools: z.array(z.string().min(1)).optional().describe("Qualified tool names to enable for this session, e.g. [\"mcp__myserver__search\"].")
+}).strict();
+/** One-line description cap for list output; keeps a fat server readable. */
+const DESCRIPTION_PREVIEW_CHARS = 160;
+function previewDescription(description) {
+	const flat = description.replaceAll(/\s+/g, " ").trim();
+	return flat.length <= DESCRIPTION_PREVIEW_CHARS ? flat : `${flat.slice(0, DESCRIPTION_PREVIEW_CHARS)}…`;
+}
+var DiscoverMcpToolsTool = class {
+	tools;
+	name = "DiscoverMcpTools";
+	description = "List and enable MCP (external) tools that are not declared by default. MCP servers are on-demand: their tool schemas stay out of the request until you enable them here. No arguments → overview of servers; `server` → that server's tools with one-line descriptions; `tools` → enable exactly those qualified names for this session (they appear from the next step on).";
+	parameters = toInputJsonSchema(DiscoverMcpToolsInputSchema);
+	constructor(tools) {
+		this.tools = tools;
+	}
+	resolveExecution(args) {
+		return {
+			description: "Discovering MCP tools",
+			approvalRule: this.name,
+			execute: async () => {
+				if (args.tools !== void 0 && args.tools.length > 0) {
+					const { enabled, skipped } = this.tools.enableDeferredMcpTools(args.tools);
+					const lines = [];
+					if (enabled.length > 0) {
+						lines.push(`enabled: ${String(enabled.length)}`);
+						lines.push(...enabled.map((name) => `- ${name}`));
+						lines.push("These tools are callable from the next step on.");
+					} else lines.push("enabled: 0");
+					if (skipped.length > 0) lines.push(`skipped: ${String(skipped.length)} (not on-demand, already enabled, or excluded by the active tool patterns)`, ...skipped.map((name) => `- ${name}`));
+					return {
+						output: lines.join("\n"),
+						isError: false
+					};
+				}
+				if (args.server !== void 0) {
+					const tools = this.tools.listDeferredMcpTools(args.server);
+					if (tools.length === 0) return {
+						output: `No on-demand tools for server "${args.server}". The server is absent, eager (\`exposure: always\`), or all of its tools are already enabled.`,
+						isError: false
+					};
+					return {
+						output: [
+							`server: ${args.server}`,
+							`tools: ${String(tools.length)}`,
+							...tools.map((t) => `- ${t.name} — ${previewDescription(t.description)}`)
+						].join("\n"),
+						isError: false
+					};
+				}
+				const tools = this.tools.listDeferredMcpTools();
+				if (tools.length === 0) return {
+					output: "No on-demand MCP tools are available. Either no MCP server is connected, every server declares its tools eagerly, or everything accessible is already enabled.",
+					isError: false
+				};
+				const byServer = /* @__PURE__ */ new Map();
+				for (const tool of tools) {
+					const names = byServer.get(tool.serverName) ?? [];
+					names.push(tool.name);
+					byServer.set(tool.serverName, names);
+				}
+				return {
+					output: [
+						`withheld_tools: ${String(tools.length)}`,
+						`servers: ${String(byServer.size)}`,
+						...[...byServer.entries()].map(([server, names]) => `- ${server}: ${String(names.length)} tool(s)`),
+						"Call again with `server` to list one server, or with `tools` to enable specific names."
+					].join("\n"),
+					isError: false
+				};
+			}
+		};
+	}
+};
+//#endregion
 //#region ../../node_modules/.pnpm/object-keys@1.1.1/node_modules/object-keys/isArguments.js
 var require_isArguments = /* @__PURE__ */ __commonJSMin(((exports, module) => {
 	var toStr = Object.prototype.toString;
@@ -66099,7 +66204,17 @@ async function resolveSkillInstallPaths(options) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/skill/registry.ts
-const LISTING_DESC_MAX = 250;
+/**
+* Character budget for one skill description inside the model skill listing
+* (the block injected into the system prompt as `SCREAM_SKILLS`).
+*
+* The listing is a discovery index, not the skill's documentation: the leading
+* sentence is enough to decide whether a skill is worth loading, and the byte
+* cost is paid on every turn of every session. The full description lives in
+* the SKILL.md body next to the skill, and becomes visible when the Skill tool
+* loads that file on demand — so nothing is lost by shortening it here.
+*/
+const SKILL_LIST_DESCRIPTION_MAX_CHARS = 300;
 var SkillRegistry = class {
 	byName = /* @__PURE__ */ new Map();
 	byPluginAndName = /* @__PURE__ */ new Map();
@@ -66317,13 +66432,19 @@ function formatFullSkill(skill) {
 	];
 }
 function formatModelSkill(skill) {
-	const lines = [`- ${skill.name}: ${truncate$2(skill.description, LISTING_DESC_MAX)}`];
+	const description = truncate$2(skill.description, SKILL_LIST_DESCRIPTION_MAX_CHARS);
+	const lines = [`- ${skill.name}: ${description}`];
 	if (typeof skill.metadata.whenToUse === "string" && skill.metadata.whenToUse.length > 0) lines.push(`  When to use: ${skill.metadata.whenToUse}`);
 	lines.push(`  Path: ${skill.path}`);
 	return lines;
 }
+/**
+* Cut `value` down to at most `max` characters, appending an ellipsis when it
+* was shortened so the model can tell the text continues in SKILL.md. The
+* ellipsis counts toward `max`, so a truncated value never exceeds the budget.
+*/
 function truncate$2(value, max) {
-	return value.length > max ? value.slice(0, max) : value;
+	return value.length > max ? `${value.slice(0, max - 1)}…` : value;
 }
 function escapeAttr$1(value) {
 	return value.replaceAll("&", "&amp;").replaceAll("\"", "&quot;");
@@ -68028,7 +68149,9 @@ const HookDefSchema = z.object({
 const DuckDuckGoConfigSchema = z.object({ enabled: z.boolean().default(true) });
 const BingSearchConfigSchema = z.object({ enabled: z.boolean().default(true) });
 const DomesticSearchConfigSchema = z.object({ enabled: z.boolean().default(true) });
+const GoogleSearchConfigSchema = z.object({ enabled: z.boolean().default(true) });
 const ServicesConfigSchema = z.object({
+	google: GoogleSearchConfigSchema.optional(),
 	duckduckgo: DuckDuckGoConfigSchema.optional(),
 	bing: BingSearchConfigSchema.optional(),
 	sogou: DomesticSearchConfigSchema.optional(),
@@ -68047,7 +68170,16 @@ const McpServerCommonFields = {
 	* `[]` = explicitly opted out of fingerprinting; non-empty = explicit
 	* declaration (highest priority). See `mcp/capabilities.ts`.
 	*/
-	capabilities: z.array(z.string().min(1)).optional()
+	capabilities: z.array(z.string().min(1)).optional(),
+	/**
+	* How this server's tools are offered to the model. `'on-demand'` (the
+	* default when unset) keeps the tool schemas out of every request: the
+	* model lists and enables them through the `DiscoverMcpTools` meta tool.
+	* `'always'` declares every tool from the first step (the behaviour
+	* before deferral). Large servers (browser automation, code indexes)
+	* routinely cost tens of thousands of tokens per request when eager.
+	*/
+	exposure: z.enum(["always", "on-demand"]).optional()
 };
 const McpServerStdioConfigSchema = z.object({
 	transport: z.literal("stdio"),
@@ -68117,7 +68249,9 @@ const BackgroundConfigPatchSchema = BackgroundConfigSchema.partial();
 const DuckDuckGoConfigPatchSchema = DuckDuckGoConfigSchema.partial();
 const BingSearchConfigPatchSchema = BingSearchConfigSchema.partial();
 const DomesticSearchConfigPatchSchema = DomesticSearchConfigSchema.partial();
+const GoogleSearchConfigPatchSchema = GoogleSearchConfigSchema.partial();
 const ServicesConfigPatchSchema = z.object({
+	google: GoogleSearchConfigPatchSchema.optional(),
 	duckduckgo: DuckDuckGoConfigPatchSchema.optional(),
 	bing: BingSearchConfigPatchSchema.optional(),
 	sogou: DomesticSearchConfigPatchSchema.optional(),
@@ -70138,7 +70272,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\nItems must be independent - no subagent depends on another's output.\nIf items depend on each other, use separate Agent calls instead.\n\nPick `subagent_type` from the generated \"Available agent types\" list below: every type states its own USE WHEN / NOT FOR, and the same rule holds for a batch (one type for every item).\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\nAll spawned subagents share one `subagent_type`, one `prompt_template` and the\nsame batch-level settings. WolfPack keeps its unlimited-concurrency contract:\nevery item spawns and runs in parallel with no artificial concurrency cap.\n\nBatch-level `output_schema` / `output_token_hint` / `capability_mode` are\nforwarded to every spawned subagent (same semantics as the `Agent` tool):\n- `output_schema` — each item result that parses as a JSON object is surfaced\n  as a `[structured]` block; non-JSON results are marked `structured: invalid`.\n- `capability_mode` — runtime tool isolation (read-only / read-write /\n  execute / all) applied to every item; restricted modes strip MCP tools and\n  nested Agent / SendSubagentMessage / WolfPack tools.\n";
+var wolfpack_default = "Use WolfPack to spawn multiple subagents in parallel for a batch of independent items (files, checks, searches) that share one `subagent_type` and one `prompt_template`. Items must not depend on each other's output — if they do, use separate `Agent` calls. There is no artificial concurrency cap: every item spawns and runs in parallel.\n\nPick `subagent_type` from the \"Available agent types\" list below; each type states its own USE WHEN / NOT FOR, and the same rule holds for a batch (one type for every item).\n\nBatch-level `output_schema` / `output_token_hint` / `capability_mode` are forwarded to every spawned subagent with the same semantics as the `Agent` tool.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/collaboration/wolfpack.ts
 /**
@@ -70150,17 +70284,17 @@ var wolfpack_default = "Use WolfPack to spawn multiple subagents in parallel for
 */
 const WolfPackToolInputSchema = z.object({
 	description: z.string().min(1).describe("Short task description (3-5 words, e.g., \"Security review all files\")"),
-	subagent_type: z.string().default("coder").describe("Subagent type for all spawned agents (e.g., coder, explore, verify)"),
-	prompt_template: z.string().min(1).describe("Prompt template with {{item}} placeholder. Each item is substituted in."),
-	items: z.array(z.string().min(1)).min(1).describe("Array of items to process. Each item gets its own subagent."),
-	output_schema: z.string().optional().describe("Optional JSON Schema (as a JSON string) describing the single JSON object each subagent should reply with. When provided, each item result that parses as a JSON object is surfaced as a [structured] block; parse failures are reported as structured: invalid alongside the raw text."),
-	output_token_hint: z.number().int().min(1).max(32768).optional().describe("Optional hint for the final-answer length of each subagent (keeps structured replies compact, e.g. 1024). Not an enforced cap."),
+	subagent_type: z.string().default("coder").describe("Subagent type for all spawned agents (see the agent-type list in the description)."),
+	prompt_template: z.string().min(1).describe("Prompt template with a {{item}} placeholder; each item is substituted in."),
+	items: z.array(z.string().min(1)).min(1).describe("Items to process — each one gets its own subagent, all running in parallel."),
+	output_schema: z.string().optional().describe("JSON Schema (as a JSON string) each subagent should answer with; parseable JSON objects surface as [structured] blocks, parse failures are reported as structured: invalid alongside the raw text."),
+	output_token_hint: z.number().int().min(1).max(32768).optional().describe("Hint for each subagent final-answer length (e.g. 1024). Not an enforced cap."),
 	capability_mode: z.enum([
 		"read-only",
 		"read-write",
 		"execute",
 		"all"
-	]).optional().describe("Runtime capability isolation applied to every spawned subagent: read-only (no writes/execution), read-write (no execution), execute (commands allowed, external side effects still gated), all (full, default). Restricted modes also strip MCP tools and nested Agent/SendSubagentMessage/WolfPack tools at runtime.")
+	]).optional().describe("Runtime capability isolation applied to every spawned subagent: read-only (no writes or execution), read-write (no execution), execute (commands allowed), all (full, default). Restricted modes also strip MCP and nested Agent/SendSubagentMessage/WolfPack tools.")
 });
 /** Default per-subagent timeout (5 minutes). */
 const DEFAULT_SUBAGENT_TIMEOUT_MS = 300 * 1e3;
@@ -74819,23 +74953,23 @@ var grep_default = "Search file contents using regular expressions (powered by r
 //#region ../../packages/agent-core/src/tools/builtin/file/grep.ts
 const GrepInputSchema = z.object({
 	pattern: z.string().describe("Regular expression to search for."),
-	path: z.string().optional().describe("File or directory to search. Accepts an absolute path, or a path relative to the current working directory. Omit to search the current working directory. Use Read instead when you already know a concrete file path and need its contents."),
-	glob: z.string().optional().describe("Optional glob filter passed to ripgrep."),
-	type: z.string().optional().describe("Optional ripgrep file type filter, such as ts or py. Prefer this over `glob` when filtering by language or file kind: it is more efficient and less error-prone than an equivalent glob pattern."),
+	path: z.string().optional().describe("File or directory to search: an absolute path, or one relative to the current working directory; omit to search the working directory. Use Read instead when you already know a concrete file path and need its contents."),
+	glob: z.string().optional().describe("Glob filter passed to ripgrep."),
+	type: z.string().optional().describe("Ripgrep file type filter, such as ts or py. Prefer this over `glob` when filtering by language or file kind: more efficient and less error-prone."),
 	output_mode: z.enum([
 		"content",
 		"files_with_matches",
 		"count_matches"
-	]).optional().describe("Shape of the result. `content` shows matching lines (honors `-A`, `-B`, `-C`, `-n`, and `head_limit`); `files_with_matches` shows only the paths of files that contain a match (honors `head_limit`); `count_matches` shows the total number of matches. Defaults to `files_with_matches`."),
-	"-i": z.boolean().optional().describe("Perform a case-insensitive search. Defaults to false."),
-	"-n": z.boolean().optional().describe("Prefix each matching line with its line number. Applies only when `output_mode` is `content`. Defaults to true."),
-	"-A": z.number().int().nonnegative().optional().describe("Number of lines to show after each match. Applies only when `output_mode` is `content`."),
-	"-B": z.number().int().nonnegative().optional().describe("Number of lines to show before each match. Applies only when `output_mode` is `content`."),
-	"-C": z.number().int().nonnegative().optional().describe("Number of lines to show before and after each match. Applies only when `output_mode` is `content`; takes precedence over `-A` and `-B`."),
-	head_limit: z.number().int().nonnegative().optional().describe("Limit output to the first N lines/entries after offset. Defaults to 250. Pass 0 for unlimited."),
-	offset: z.number().int().nonnegative().optional().describe("Number of leading lines/entries to skip before applying `head_limit`. Use it together with `head_limit` to page through large result sets. Defaults to 0."),
-	multiline: z.boolean().optional().describe("Enable multiline matching, where the pattern can span line boundaries and `.` also matches newlines. Defaults to false."),
-	include_ignored: z.boolean().optional().describe("Also search files excluded by ignore files such as `.gitignore`, `.ignore`, and `.rgignore` (for example `node_modules` or build outputs). Sensitive files (such as `.env`) remain filtered out for safety. Defaults to false.")
+	]).optional().describe("Shape of the result. `content` shows matching lines (honors `-A`, `-B`, `-C`, `-n`, `head_limit`); `files_with_matches` shows only paths of files with a match (honors `head_limit`); `count_matches` shows the total match count. Defaults to `files_with_matches`."),
+	"-i": z.boolean().optional().describe("Case-insensitive search. Defaults to false."),
+	"-n": z.boolean().optional().describe("Prefix each matching line with its line number; applies only when `output_mode` is `content`. Defaults to true."),
+	"-A": z.number().int().nonnegative().optional().describe("Lines to show after each match; applies only when `output_mode` is `content`."),
+	"-B": z.number().int().nonnegative().optional().describe("Lines to show before each match; applies only when `output_mode` is `content`."),
+	"-C": z.number().int().nonnegative().optional().describe("Lines to show before and after each match; applies only when `output_mode` is `content`, and takes precedence over `-A` and `-B`."),
+	head_limit: z.number().int().nonnegative().optional().describe("Limit output to the first N lines/entries after offset. Defaults to 250; 0 means unlimited."),
+	offset: z.number().int().nonnegative().optional().describe("Leading lines/entries to skip before `head_limit` — use it with `head_limit` to page through large results. Defaults to 0."),
+	multiline: z.boolean().optional().describe("Multiline matching: the pattern may span lines and `.` also matches newlines. Defaults to false."),
+	include_ignored: z.boolean().optional().describe("Also search files excluded by ignore files such as `.gitignore`, `.ignore`, and `.rgignore` (e.g. `node_modules` or build output). Sensitive files (such as `.env`) stay filtered out. Defaults to false.")
 });
 z.object({
 	mode: z.enum([
@@ -76931,10 +77065,10 @@ 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\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";
+var enter_plan_mode_default = "Use this tool proactively when you're about to start a non-trivial implementation task: getting user sign-off on your approach via ExitPlanMode before writing code prevents wasted effort.\n\n## Planning Modes\n\n- **Normal plan**: investigate the codebase, design a single approach, write it to the plan file, then present it for approval.\n- **Fusion plan**: call the FusionPlan tool to spawn parallel planning subagents that each explore a different angle, then synthesize their output into one plan. Slower, but it tends to surface risks and alternatives you would otherwise miss.\n\nPrefer **normal plan** for specific detailed instructions, small or localized changes (1-3 files), a codebase you know well, or when speed matters; prefer **fusion plan** for open-ended or ambiguous tasks (\"improve performance\", \"refactor auth\"), multiple valid architectures, changes spanning more than 3-5 files or touching core abstractions, and when you want parallel exploration. If unsure: normal for small fixes, fusion for larger design tasks.\n\n## When to Use\n\nUse it when any of these apply: new feature implementation; multiple valid approaches; code modifications to existing modules; architectural decisions; multi-file changes (more than 2-3 files); unclear requirements that need exploration; decisions where the user's preference would materially change the approach.\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; in auto permission mode it exits without asking, and you should not use AskUserQuestion there — decide from the available context.\n- Use EnterPlanMode only when planning itself adds value.\n\nWhen NOT to use: single-line or few-line fixes (typos, obvious bugs, small tweaks), very specific detailed instructions from the user, or pure research/exploration tasks.\n\n## What Happens in Plan Mode\n\n1. Identify the 2-3 key questions about the codebase that are critical to your plan. If you are not confident about the structure or the relevant code paths, use `Agent(subagent_type=\"explore\")` to investigate them first — strongly recommended for non-trivial tasks.\n2. Do the remaining quick lookups with Glob, Grep, Read and the other read-only tools; use Bash only when needed (it follows the normal permission mode and rules).\n3. Design the implementation approach from your findings — for fusion plan, call FusionPlan to generate the synthesized plan.\n4. Review the plan, fill in any gaps, check it matches the user's intent, then present it via ExitPlanMode for approval.\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();
+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 one plan for you to review — use it for ambiguous, large, or multi-approach tasks.") }).strict();
 var EnterPlanModeTool = class {
 	agent;
 	name = "EnterPlanMode";
@@ -77502,7 +77636,7 @@ function messageOf(error) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/plugin/manage-plugin.md
-var manage_plugin_default = "Manage this product's own plugins. Plugins are the vehicle for add-on capabilities: each one can contribute skills, MCP servers, shell hooks, and — only after an explicit activate — code that runs in this process.\n\nUse this tool in two situations: (a) a task needs a capability you do not currently have — exhaust your existing tools first and add a plugin only when the gap is real; (b) the user asks you to find, install, configure, inspect, or clean up a capability (e.g. \"install something that can render mermaid\", \"disable the plugin I no longer use\"). In both cases, remove or disable additions again when the work is done unless the capability is broadly reusable.\n\n**Not for inventory questions**: when the user asks what you have — in any wording (skills / plugins / capabilities / MCP / tools / 技能 / 插件 / 能力) — answer with **InspectOwnAssets** (the read-only inventory: every skill package on disk with live `invocable` status, plus MCP declarations). `{\"action\":\"list\"}` here is the **plugin management view**: a pre-change check of the plugin table before installing or modifying, not the answer to \"what can you do\".\n\nChoose the lightest vehicle that solves the problem, in this order: a skill (prompt instructions — safest, no code, no process), an MCP server (an external process), a code plugin (runs in this process — the most powerful, needs its own approved `activate`).\n\n## Workflow\n\n1. `{\"action\":\"list\"}` — see what is already installed before adding anything. To confirm the gap is real, start from an `InspectOwnAssets` inventory (what exists on disk and what is invocable), then check this table for an existing plugin that already covers it. Do not grow a second plugin that duplicates an existing capability; enable, disable, or extend the one you already have.\n2. `{\"action\":\"marketplace\",\"query\":\"pdf\"}` — browse the catalog for a matching capability. Pass `source` to read a different catalog. `tier` is a display label only; judge an entry by its description and source. Entries whose origin previously produced a tripped plugin carry `quarantined: true`.\n3. `{\"action\":\"precheck\",\"source\":\"https://github.com/owner/repo\"}` — free read-only origin check before installing anything external that you have not vetted in this session: it reports past incidents recorded by the plugin center's immune memory (`quarantined:true` + the reason). Surface such a warning to the user BEFORE asking for the install approval.\n4. If nothing in the catalog fits and precheck is clean, you may search the web (`WebSearch` / `FetchURL`) and evaluate a repository yourself: read its README and manifest, prefer a pinned branch/tag/commit URL over a moving default, and check that it does something you cannot already do.\n5. To **make a capability yourself**: if the user invoked `/make-skill`, use the `MakeSkillPlan` → `MakeSkillApply` pair (it produces a valid skill package and registers it into this table automatically). Otherwise build a plugin directory by hand (a `scream.plugin.json` manifest plus your SKILL.md under `skills/`) and register it with `register_generated` — that route lands in this table, hot-applies the same turn, and stays manageable here (disable/remove/circuit). Writing a plain SKILL.md into the user skills directory is also a legitimate skill, but it does NOT appear in this table and cannot be managed with this tool.\n6. `{\"action\":\"install\",\"source\":\"https://github.com/owner/repo/tree/v1.2.0\"}` — install from a local path, a GitHub URL, or a zip URL. **Installing never executes code.** The plugin's files are copied and its record is registered; a manifest `entryPoint` stays dormant until step 8.\n7. `{\"action\":\"install\",\"source\":\"...\",\"upgrade\":true}` — same-name refresh: backs up the current files (single slot under `plugins/backups/<id>/`), swaps in the new ones, and reloads; `from`/`to` versions and any downgrade warning are reported. If activation then fails, `rollback` restores the previous files in one approved step.\n8. `{\"action\":\"enable\",\"id\":\"...\"}` / `{\"action\":\"disable\",\"id\":\"...\"}` / `{\"action\":\"set_mcp_enabled\",\"id\":\"...\",\"server\":\"...\",\"enabled\":false}` — turn contributed capabilities on and off.\n9. `{\"action\":\"activate\",\"id\":\"...\"}` — the only action that runs a plugin's code entry point in this process. Skip it for skill-only and MCP-only plugins; they need no activation.\n10. `{\"action\":\"info\",\"id\":\"...\"}` / `{\"action\":\"check\"}` — inspect one record in full, or the health of the table. Each entry also carries `usage: {calls, okCalls, okRate, lastUsedAt}` from this machine: zero calls since install marks it as a cleanup candidate; high usage with a high okRate is worth keeping when you must choose.\n11. `{\"action\":\"reset\",\"id\":\"...\"}` — recover a circuit-tripped or manually disabled plugin: clears its failure ledger, re-derives the record from disk, enables it, and hot-applies its capabilities. It never runs code — a code plugin still needs its own approved `activate`.\n12. `{\"action\":\"rollback\",\"id\":\"...\"}` — restore the pre-upgrade backup taken by step 7 in one approved step.\n13. `{\"action\":\"reload\"}` — re-read the plugin table from disk and get an added/removed/error summary.\n14. `{\"action\":\"remove\",\"id\":\"...\"}` (or `disable` to keep the record) — retreat once the capability is no longer wanted.\n\n## Circuit breaker (limbs that fail get pulled, the loop never dies)\n\nPlugin-owned capabilities are counted per plugin: every failed tool call (in-process plugin tools and plugin MCP servers) and every faulty event handler. A success clears the streak; three consecutive failures trip the breaker, and the failing result arrives with a `[circuit]` advisory: the plugin was marked with the reason, disabled persistently, its code deactivated, and its tools, MCP servers, skills, and hooks pulled from every live session. Nothing retries automatically — read the state with `check` (each plugin carries `circuit: {failures, tripped}`), then `reset` to give it another chance or `remove` to let it go. User-configured MCP servers and built-in tools are never charged to anyone's breaker.\n\nEvery trip ALSO writes the origin into the plugin center's immune memory (quarantine ledger): future `precheck`/`install`/`marketplace` calls for the same repository will surface that history before anything is executed again, even across sessions — and even if the broken plugin was removed afterwards.\n\nChanges are hot-applied to the running session wherever the host supports it: mutating results carry a `sync` report (`{ok, applied[], failed[]}`) naming exactly what landed — `skills.inject`, `mcp.add`/`mcp.remove`, tool teardown. An `install` deliberately reports no `mcp.add`: installing never starts a plugin's MCP process; that waits for an approved `enable`/`activate`/`reload`. Treat `sync.failed` as advisory (the mutation itself already succeeded) and re-check with `info`/`check` rather than re-running the mutation. Reload before judging whether a change landed.\n\n## Registration of your own output\n\n`{\"action\":\"register_generated\",\"source\":\"/abs/path/to/generated/plugin\"}` registers a plugin directory you produced locally, without a copy step. It refuses any manifest that declares an `entryPoint`: this action is normally auto-approved and must never become a route to running code. For a code plugin, use `install` and then `activate`.\n\n## Approval contract\n\n- Read-only actions (`list`, `info`, `check`, `marketplace`) run without prompting.\n- Every mutating action (`install`, `register_generated`, `enable`, `disable`, `set_mcp_enabled`, `activate`, `deactivate`, `remove`, `reset`, `reload`) requires the user's approval. State what you are about to do and why in one line, then call the tool — never describe a plugin change you have not made.\n- The approval prompt for `install` and `register_generated` shows the full source string, and a session grant applies to that exact source only.\n- `activate` is the step that executes third-party code; treat it as its own decision, made after you have read what the plugin does.\n- A rejected approval is an answer, not a retry cue. Report the refusal and continue without the capability.\n\n## Output\n\nEvery action returns a JSON string. Success is a compact result object; failure is\n`{\"error\":{\"code\",\"message\",\"next\"}}` with `isError: true`. Follow `next` rather than\nguessing at a repair — it names the call that resolves the problem.\n";
+var manage_plugin_default = "Manage this product's own plugins — the vehicle for add-on capabilities: a plugin can contribute skills, MCP servers, shell hooks, and (only after an explicit `activate`) code that runs in this process.\n\nUse it when a task needs a capability you do not have (exhaust your existing tools first, and remove or disable the addition when the work is done unless it is broadly reusable), or when the user asks you to find, install, configure, inspect, or clean up a capability. For \"what can you do\" questions answer with **InspectOwnAssets** instead — `{\"action\":\"list\"}` here is the plugin-management view, a pre-change check of the plugin table. Prefer the lightest vehicle: a skill (prompt only), then an MCP server (external process), then a code plugin (needs an approved `activate`).\n\nActions: `list`; `marketplace` / `precheck` (browse the catalog / free read-only origin check reporting incidents from the plugin center's immune memory, `quarantined:true` plus the reason — run it before installing anything you have not vetted this session, and surface such a warning to the user BEFORE asking for the install approval); `install` (local path, GitHub URL, or zip URL — **installing never executes code**; `upgrade:true` backs up the current files first); `register_generated` (register a directory you built — it refuses any manifest declaring an `entryPoint`, since it is normally auto-approved and must never become a route to running code); `enable` / `disable` / `set_mcp_enabled`; `activate` / `deactivate` (the only actions that run a plugin's code entry point — skip for skill-only and MCP-only plugins); `info` / `check` (one record / table health); `reset` (recover a tripped or disabled plugin — clears the failure ledger, re-derives from disk, enables and hot-applies, never runs code); `rollback`; `reload`; `remove`. `id` is required by info, enable, disable, set_mcp_enabled, activate, deactivate, remove, reset and rollback.\n\nApproval contract: read-only actions (`list`, `info`, `check`, `marketplace`, `precheck`) run without prompting; every mutating action requires the user's approval — state what you are about to do in one line, then call it. The prompt shows the full source string for `install`/`register_generated`, and a session grant covers that exact source only. `activate` executes third-party code and is its own decision. A rejected approval is an answer, not a retry cue.\n\nCircuit breaker: every failed plugin-owned call and faulty event handler counts against its plugin; three consecutive failures trip it — the plugin is marked with the reason, disabled persistently, its code deactivated, and its tools/MCP servers/skills/hooks pulled from live sessions, with a `[circuit]` advisory on the failing result. Nothing retries automatically: read `circuit:{failures, tripped}` with `check`, then `reset` or `remove`. A trip is also written into the quarantine ledger, so later `precheck`/`install`/`marketplace` calls for the same repository surface that history even across sessions.\n\nMutating actions hot-apply where the host supports it and report `sync:{ok, applied[], failed[]}` naming what landed (`skills.inject`, `mcp.add`/`mcp.remove`, tool teardown); `install` reports no `mcp.add`, because installing never starts a plugin's MCP process. Treat `sync.failed` as advisory and re-check with `info`/`check` instead of re-running the mutation. Every action returns JSON; a failure is `{\"error\":{\"code\",\"message\",\"next\"}}` — follow `next` rather than guessing at a repair.\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/plugin/manage-plugin.ts
 /** Every action this tool understands. */
@@ -77537,9 +77671,9 @@ const MANAGE_PLUGIN_READ_ONLY_ACTIONS = [
 ];
 const ManagePluginInputSchema = z.object({
 	action: z.enum(MANAGE_PLUGIN_ACTIONS).describe("Which plugin operation to run."),
-	id: z.string().optional().describe("Plugin id. Required for info, check, enable, disable, set_mcp_enabled, activate, deactivate, remove, reset."),
-	source: z.string().optional().describe("install: absolute path / GitHub URL / zip URL. register_generated: the generated plugin directory. marketplace: optional catalog URL or local JSON path."),
-	upgrade: z.boolean().optional().describe("install onto an existing plugin id: back up its current files, replace with the incoming ones, and reload. Without it, installing over an existing id silently overwrites."),
+	id: z.string().optional().describe("Plugin id — required by info, enable, disable, set_mcp_enabled, activate, deactivate, remove, reset, rollback."),
+	source: z.string().optional().describe("install: absolute path, GitHub URL, or zip URL. register_generated: the generated directory. marketplace: optional catalog URL or local JSON path."),
+	upgrade: z.boolean().optional().describe("install over an existing id: back up its files, replace, reload. Without it, installing over an existing id overwrites silently."),
 	server: z.string().optional().describe("MCP server name, for set_mcp_enabled."),
 	enabled: z.boolean().optional().describe("Target state, for set_mcp_enabled."),
 	query: z.string().optional().describe("Case-insensitive substring filter, for marketplace.")
@@ -79231,7 +79365,7 @@ function splitSegments(value) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/shell/bash.md
-var bash_default = "Execute a `{{ SHELL_NAME }}` command. Use this for shell semantics — pipes, env, processes, git, package managers, build/test runners, anything genuinely interactive or multi-step.\n\n**Translate these to a dedicated tool instead:**\n- `cat` / `head` / `tail` (known path) → `Read`\n- `sed` / `awk` (in-place edit) → `Edit`\n- `echo > file` / `cat <<EOF` → `Write`\n- `find` / recursive `ls` to locate files by name pattern → `Glob` (plain `ls <known-directory>` is fine for listing a directory)\n- `grep` / `rg` (search file contents) → `Grep`\n- `echo` / `printf` (talk to the user) → just output text directly\n\nThe dedicated tools render in the per-tool permission UI and keep raw stdout out of the conversation; that is why they are worth reaching for whenever one fits.\n\n**Output:**\nThe stdout and stderr will be combined and returned as a string. The output may be truncated if it is too long. If the command failed, the output will end with a `Command failed with exit code: N` line stating the non-zero exit code.\n\nIf `run_in_background=true`, the command will be started as a background task and this tool will return a task ID instead of waiting for command completion. When doing that, you must provide a short `description`. Background commands default to a {{ DEFAULT_BACKGROUND_TIMEOUT_S }}s timeout and `timeout` is capped at {{ MAX_BACKGROUND_TIMEOUT_S }}s; set `disable_timeout=true` only when the task should run without a timeout. You will be automatically notified when the task completes. Use `TaskOutput` for a non-blocking status/output snapshot, and only set `block=true` when you explicitly want to wait for completion. Use `TaskStop` only if the task must be cancelled. If a human user wants to inspect background tasks themselves, point them to the `/tasks` command, which opens an interactive panel; it has no subcommands.\n\n**Guidelines for safety and security:**\n- Each shell tool call will be executed in a fresh shell environment. The shell variables, current working directory changes, and the shell history is not preserved between calls.\n- The tool call will return after the command is finished. You shall not use this tool to execute an interactive command or a command that may run forever. For possibly long-running foreground commands, set the `timeout` argument in seconds. Foreground commands default to {{ DEFAULT_TIMEOUT_S }}s and allow up to {{ MAX_TIMEOUT_S }}s.\n- Avoid using `..` to access files or directories outside of the working directory.\n- Avoid modifying files outside of the working directory unless explicitly instructed to do so.\n- Never run commands that require superuser privileges unless explicitly instructed to do so.\n\n**Guidelines for efficiency:**\n{%- if SHELL_IS_POWERSHELL %}\n- Chain with `;` to run commands sequentially. `&&` / `||` only exist from PowerShell 7 and are a parse error on Windows PowerShell 5.1, so do not use them; write `; if ($?) { … }` when the next step must run only if the previous one succeeded.\n- Filter and transform with pipelines (`Get-ChildItem | Where-Object …`); redirect with `>` / `>>`.\n- Quote paths containing spaces with single quotes, e.g. `Set-Location 'C:\\Program Files'`.\n- Read environment variables as `$env:NAME` (`$env:NAME = 'value'`), never `$NAME`.\n- Compose multi-step logic in a single call with `if` / `foreach` / `while` and `try` / `catch`.\n{%- else %}\n- For multiple related commands, use `&&` to chain them in a single call, e.g. `cd /path && ls -la`\n- Use `;` to run commands sequentially regardless of success/failure\n- Use `||` for conditional execution (run second command only if first fails)\n- Use pipe operations (`|`) and redirections (`>`, `>>`) to chain input and output between commands\n- Always quote file paths containing spaces with double quotes (e.g., cd \"/path with spaces/\")\n- Compose multi-step logic in a single call with `if` / `case` / `for` / `while` control flows.\n{%- endif %}\n- Prefer `run_in_background=true` for long-running builds, tests, watchers, or servers when you need the conversation to continue before the command finishes.\n\n**Commands available:**\nThe following common command categories are usually available. Availability still depends on the host, so when in doubt {% if SHELL_IS_POWERSHELL %}confirm a command exists with `Get-Command <name> -ErrorAction SilentlyContinue` before relying on it — several names below are cmdlet aliases (`ls` → `Get-ChildItem`, `rm` → `Remove-Item`), and POSIX-only entries such as `uname`, `chmod` and `kill` may be absent.{% else %}run `which <command>` first to confirm a command exists before relying on it.{% endif %}\n- Navigation and inspection: `ls`, `pwd`, `cd`, `stat`, `file`, `du`, `df`, `tree`\n- File and directory management: `cp`, `mv`, `rm`, `mkdir`, `touch`, `ln`, `chmod`, `chown`\n- Text and data processing: `wc`, `sort`, `uniq`, `cut`, `tr`, `diff`, `xargs`\n- Archives and compression: `tar`, `gzip`, `gunzip`, `zip`, `unzip`\n- Networking and transfer: `curl`, `wget`, `ping`, `ssh`, `scp`\n- Version control: `git`\n- Process and system: `ps`, `kill`, `top`, `env`, `date`, `uname`, `whoami`\n- Language and package toolchains: `node`, `npm`, `pnpm`, `yarn`, `python`, `pip` (use whichever the project actually relies on)\n";
+var bash_default = "Execute a `{{ SHELL_NAME }}` command. Use this for shell semantics — pipes, env, processes, git, package managers, build/test runners, anything genuinely interactive or multi-step.\n\n**Translate these to a dedicated tool instead:** `cat` / `head` / `tail` on a known path → `Read`; in-place `sed` / `awk` → `Edit`; `echo > file` / `cat <<EOF` → `Write`; `find` / recursive `ls` to locate files by name → `Glob` (a plain `ls <known-directory>` is fine); searching contents with `grep` / `rg` → `Grep`; talking to the user with `echo` / `printf` → just output text.\n\n**Output:** stdout and stderr come back combined, truncated when too long; a failed command ends with a `Command failed with exit code: N` line.\n\nIf `run_in_background=true`, the command starts as a background task and this tool returns a task ID instead of waiting — give a short `description` when you do that. Background commands default to a {{ DEFAULT_BACKGROUND_TIMEOUT_S }}s timeout (`timeout` capped at {{ MAX_BACKGROUND_TIMEOUT_S }}s); set `disable_timeout=true` only when the task should run without one. You are automatically notified when the task completes: use `TaskOutput` for a non-blocking status snapshot (`block=true` to wait deliberately), `TaskStop` only to cancel, and point a human who wants to inspect background tasks at `/tasks` (an interactive panel).\n\n**Guidelines for safety and security:**\n- Each call runs in a fresh shell: variables, `cd` changes, and shell history are not preserved between calls.\n- Never run an interactive command or one that may run forever. For possibly long-running foreground commands set `timeout` (in seconds): the default is {{ DEFAULT_TIMEOUT_S }}s and foreground commands allow up to {{ MAX_TIMEOUT_S }}s.\n- Stay inside the working directory: avoid `..`, and avoid modifying files outside it unless explicitly instructed. Never run commands that require superuser privileges unless explicitly instructed.\n\n**Guidelines for efficiency:**\n{%- if SHELL_IS_POWERSHELL %}\n- Chain with `;` to run commands sequentially. `&&` / `||` exist only from PowerShell 7 and are a parse error on Windows PowerShell 5.1, so write `; if ($?) { … }` when the next step must run only if the previous one succeeded.\n- Filter and transform with pipelines (`Get-ChildItem | Where-Object …`); redirect with `>` / `>>`; quote paths containing spaces with single quotes.\n- Read environment variables as `$env:NAME` (`$env:NAME = 'value'`), never `$NAME`; compose multi-step logic in a single call with `if` / `foreach` / `while` and `try` / `catch`.\n{%- else %}\n- For multiple related commands, chain them in one call with `&&`, e.g. `cd /path && ls -la`; use `;` to run sequentially regardless of success, and `||` for conditional execution.\n- Use pipes (`|`) and redirections (`>`, `>>`) to chain input and output; quote paths containing spaces in double quotes; compose multi-step logic in a single call with `if` / `case` / `for` / `while`.\n{%- endif %}\n- Prefer `run_in_background=true` for long-running builds, tests, watchers, or servers when you need the conversation to continue before the command finishes.\n\n**Commands available:** the host's usual standard tools. When in doubt about a name, {% if SHELL_IS_POWERSHELL %}confirm it exists with `Get-Command <name> -ErrorAction SilentlyContinue` — several names are cmdlet aliases (`ls` → `Get-ChildItem`) and POSIX-only tools may be absent.{% else %}run `which <command>` first.{% endif %}\n";
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/shell/bash.ts
 /**
@@ -79319,11 +79453,11 @@ const DEFAULT_SHELL_ARGS = {
 };
 const BashInputSchema = z.object({
 	command: z.string().min(1, "Command cannot be empty.").describe("The command to execute."),
-	cwd: z.string().optional().describe("The working directory in which to run the command. When omitted, the command runs in the session's working directory."),
-	timeout: z.number().int().positive().default(DEFAULT_TIMEOUT_S).describe(`Optional timeout in seconds for the command to execute. Foreground default ${String(DEFAULT_TIMEOUT_S)}s, max ${String(MAX_TIMEOUT_S)}s. Background default ${String(DEFAULT_BACKGROUND_TIMEOUT_S)}s, max ${String(MAX_BACKGROUND_TIMEOUT_S)}s. Ignored for background commands when disable_timeout=true.`).optional(),
-	description: z.string().optional().describe("A short description for the background task. Required when run_in_background is true."),
+	cwd: z.string().optional().describe("Working directory; defaults to the session's working directory."),
+	timeout: z.number().int().positive().default(DEFAULT_TIMEOUT_S).describe(`Timeout in seconds. Foreground: default ${String(DEFAULT_TIMEOUT_S)}, max ${String(MAX_TIMEOUT_S)}. Background: default ${String(DEFAULT_BACKGROUND_TIMEOUT_S)}, max ${String(MAX_BACKGROUND_TIMEOUT_S)}; ignored when disable_timeout=true.`).optional(),
+	description: z.string().optional().describe("Short background-task description. Required when run_in_background is true."),
 	run_in_background: z.boolean().optional().describe("Whether to run the command as a background task."),
-	disable_timeout: z.boolean().optional().describe("If true, do not apply a timeout to the command. Only applies when run_in_background is true.")
+	disable_timeout: z.boolean().optional().describe("No timeout at all. Only applies when run_in_background is true.")
 }).superRefine((val, ctx) => {
 	if (val.timeout === void 0) return;
 	const isBackground = val.run_in_background === true;
@@ -79374,7 +79508,7 @@ function renderBashDescription(shellName, isPowerShell) {
 * first: the result must not depend on how the template file was checked out.
 */
 function withoutBackgroundDescription(description) {
-	return description.replaceAll("\r\n", "\n").replace(/\n\nIf `run_in_background=true`,[\s\S]*?point them to the `\/tasks` command, which opens an interactive panel; it has no subcommands\./, "\n\nBackground execution is disabled for this agent. Do not set `run_in_background=true`.").replace(` For possibly long-running foreground commands, set the \`timeout\` argument in seconds. Foreground commands default to ${String(DEFAULT_TIMEOUT_S)}s and allow up to ${String(MAX_TIMEOUT_S)}s.`, ` For possibly long-running commands, set the \`timeout\` argument in seconds. The default is ${String(DEFAULT_TIMEOUT_S)}s; foreground commands allow up to ${String(MAX_TIMEOUT_S)}s.`).replace(/\n- Prefer `run_in_background=true`[\s\S]*?conversation to continue before the command finishes\./, "\n- Do not set `run_in_background=true`; background task management tools are not available.");
+	return description.replaceAll("\r\n", "\n").replace(/\n\nIf `run_in_background=true`,[\s\S]*?at `\/tasks` \(an interactive panel\)\./, "\n\nBackground execution is disabled for this agent. Do not set `run_in_background=true`.").replace(` For possibly long-running foreground commands set \`timeout\` (in seconds): the default is ${String(DEFAULT_TIMEOUT_S)}s and foreground commands allow up to ${String(MAX_TIMEOUT_S)}s.`, ` For possibly long-running commands, set the \`timeout\` argument in seconds. The default is ${String(DEFAULT_TIMEOUT_S)}s; foreground commands allow up to ${String(MAX_TIMEOUT_S)}s.`).replace(/\n- Prefer `run_in_background=true`[\s\S]*?conversation to continue before the command finishes\./, "\n- Do not set `run_in_background=true`; background task management tools are not available.");
 }
 function rejectDangerousCommand(pattern, hint) {
 	return {
@@ -86818,6 +86952,10 @@ const MCP_CAPABILITY_GUIDES = [{
 ## Browser Automation (chrome-devtools-mcp)
 
 A Chrome DevTools MCP server is connected (\`mcp__chrome_devtools__*\` tools).
+Its tools are **on-demand**: the schemas are withheld to keep requests lean.
+Enable the ones you need first — \`DiscoverMcpTools({ server: "chrome-devtools" })\`
+lists them, then \`DiscoverMcpTools({ tools: [...] })\` makes them callable from
+the next step on.
 It drives a live Chrome instance for testing, debugging and performance
 analysis. Every page-scoped tool needs its \`pageId\`; use \`list_pages\` to
 see which pages exist.
@@ -86917,7 +87055,7 @@ function createMcpCapabilityGuideInjectors(agent) {
 const AUTO_MODE_ENTER_REMINDER = [
 	"Auto permission mode is active. Tool approvals will be handled automatically while this mode remains enabled.",
 	"  - Continue normally without pausing for approval prompts.",
-	"  - Do NOT call AskUserQuestion while auto mode is active. Make a reasonable decision and continue without asking the user."
+	"  - Do NOT call AskUserQuestion while auto mode is active — the tool is blocked. When a decision genuinely requires the user, stop that direction, state the question and your recommended option in a normal text reply, and end the turn; otherwise decide and continue."
 ].join("\n");
 const AUTO_MODE_EXIT_REMINDER = ["Auto permission mode is no longer active. Tool approvals and permission checks are back to the current mode.", "  - Continue normally, but expect approval prompts or denials when a tool requires them."].join("\n");
 const ASK_MODE_ENTER_REMINDER = [
@@ -87254,29 +87392,36 @@ function isTodoStatus(value) {
 //#region ../../packages/agent-core/src/agent/injection/user-prefs.ts
 const USER_PREFS_VARIANT = "user_prefs";
 /**
-* Injects the user's /like preferences as a system-reminder at the start of
-* every turn (i.e. after each new user prompt). The system prompt already
-* carries the preferences via {{ ROLE_ADDITIONAL }}, but that block is far
-* from the model's attention by mid-conversation. This reminder keeps the
-* preferences visible right before each response.
+* Injects the user's /like preferences as a system-reminder. The system prompt
+* already carries the preferences via {{ ROLE_ADDITIONAL }}; this reminder
+* exists so mid-conversation turns do not lose them.
 *
 * Fires when:
-*   - user-prefs.md exists and is non-empty
-*   - at least one real user prompt has arrived since the last injection
+*   - user-prefs.md exists and is non-empty, and
+*   - the previous reminder left the context (compaction/undo/clear), or
+*   - the preferences changed since the last injection.
+*
+* An identical copy is NOT re-sent every turn: repeating the same 1.6 KB
+* block after every user message was pure token cost — history accumulated
+* one duplicate per prompt while the content never changed.
 */
 var UserPrefsInjector = class extends DynamicInjector {
 	injectionVariant = USER_PREFS_VARIANT;
+	lastInjectedText = null;
 	async getInjection() {
 		if (this.injectedAt !== null && !this.hasNewUserPromptSince(this.injectedAt)) return;
 		const prefs = await loadRoleAdditional(this.agent.jian);
 		if (prefs === void 0) return void 0;
-		return [
+		const text = [
 			"USER PREFERENCES REMINDER: Before responding, re-read and apply EVERY",
 			"user preference below. These are direct user instructions set via /like",
 			"— violating them is equivalent to ignoring an explicit user request.",
 			"",
 			prefs
 		].join("\n");
+		if (this.injectedAt !== null && text === this.lastInjectedText) return void 0;
+		this.lastInjectedText = text;
+		return text;
 	}
 	hasNewUserPromptSince(from) {
 		const history = this.agent.context.history;
@@ -87329,16 +87474,21 @@ var WolfPackModeInjector = class extends DynamicInjector {
 };
 //#endregion
 //#region ../../packages/agent-core/src/agent/injection/working-set.ts
-const WORKING_SET_REMINDER_INTERVAL = 3;
+/**
+* Injects the file list the turn has touched as a "Working Set" reminder.
+*
+* Injects when the set actually changed since the last injection, or when the
+* previous copy left the context (compaction/undo/clear → `injectedAt` null).
+* The old rule was "every 3 assistant turns" — it re-sent an identical
+* ~1.4 KB block on a timer, accumulating duplicates in history.
+*/
 var WorkingSetInjector = class extends DynamicInjector {
 	injectionVariant = "working-set";
+	lastInjectedText = null;
 	getInjection() {
 		const paths = this.agent.workingSet.getPaths();
 		if (paths.length === 0) return void 0;
-		if (this.injectedAt !== null) {
-			if (this.countAssistantTurnsSince(this.injectedAt) < WORKING_SET_REMINDER_INTERVAL) return void 0;
-		}
-		return [
+		const text = [
 			"## Working Set",
 			"",
 			"当前任务可能涉及以下文件：",
@@ -87346,12 +87496,9 @@ var WorkingSetInjector = class extends DynamicInjector {
 			"",
 			"优先检查这些文件，避免重复读取未修改文件。"
 		].join("\n");
-	}
-	countAssistantTurnsSince(from) {
-		let count = 0;
-		const history = this.agent.context.history;
-		for (let i = from; i < history.length; i++) if (history[i]?.role === "assistant") count++;
-		return count;
+		if (this.injectedAt !== null && text === this.lastInjectedText) return void 0;
+		this.lastInjectedText = text;
+		return text;
 	}
 };
 //#endregion
@@ -87505,7 +87652,7 @@ var AutoModeAskUserQuestionDenyPermissionPolicy = class {
 		if (context.toolCall.name !== "AskUserQuestion") return;
 		return {
 			kind: "deny",
-			message: "AskUserQuestion is disabled while auto permission mode is active. Make a reasonable decision and continue without asking the user."
+			message: "AskUserQuestion is unavailable in auto permission mode. Decide reasonable defaults and keep working — but when a decision genuinely requires the user, stop that direction, state the question and your recommended option in a normal text reply, and end the turn so the user can answer when they return. Do not keep guessing past a question only the user can settle."
 		};
 	}
 };
@@ -87857,6 +88004,7 @@ var BotModePermissionPolicy = class BotModePermissionPolicy {
 const READ_TOOLS = new Set([
 	"AskUserQuestion",
 	"ContactParent",
+	"DiscoverMcpTools",
 	"FetchURL",
 	"Glob",
 	"Grep",
@@ -87922,6 +88070,7 @@ const DEFAULT_AUTO_APPROVE_TOOLS = new Set([
 	"Glob",
 	"ReadMediaFile",
 	"InspectOwnAssets",
+	"DiscoverMcpTools",
 	"SetTodoList",
 	"TodoList",
 	"TaskList",
@@ -88081,6 +88230,19 @@ var DefaultToolApprovePermissionPolicy = class {
 	}
 };
 //#endregion
+//#region ../../packages/agent-core/src/agent/permission/policies/destructive-hint-ask.ts
+var DestructiveHintAskPermissionPolicy = class {
+	name = "destructive-hint-ask";
+	evaluate(context) {
+		if (context.tool?.annotations?.destructiveHint !== true) return void 0;
+		return {
+			kind: "ask",
+			reasons: [`${context.toolCall.name} declares itself destructive (author-declared hint) — confirm before it runs.`],
+			grantOptions: ["once", "session"]
+		};
+	}
+};
+//#endregion
 //#region ../../packages/agent-core/src/agent/permission/policies/exit-plan-mode-review-ask.ts
 var ExitPlanModeReviewAskPermissionPolicy = class {
 	agent;
@@ -88815,6 +88977,7 @@ function createPermissionDecisionPolicies(agent) {
 		new GitControlPathAccessAskPermissionPolicy(agent),
 		new CwdOutsideFileWriteAskPermissionPolicy(agent),
 		new WolfPackModeApprovePermissionPolicy(agent),
+		new DestructiveHintAskPermissionPolicy(),
 		new DefaultToolApprovePermissionPolicy(),
 		new ManagePluginReadOnlyApprovePermissionPolicy(),
 		new GitCwdWriteApprovePermissionPolicy(agent),
@@ -88843,6 +89006,14 @@ var PermissionManager = class {
 	localPendingPrivateReads = /* @__PURE__ */ new Map();
 	localTaintedPrivateReads = /* @__PURE__ */ new Set();
 	nextApprovalId = 0;
+	/**
+	* Tools whose approval already timed out in the current turn. The user was
+	* away once for this tool; asking again would stall for another full
+	* timeout, so a second request is denied outright with guidance (see
+	* `requestToolApproval`). Reset when the turn id changes; never persisted.
+	*/
+	approvalTimeoutTurnId;
+	approvalTimeoutTools = /* @__PURE__ */ new Set();
 	constructor(agent, options = {}) {
 		this.agent = agent;
 		this.rules = [...options.initialRules ?? []];
@@ -89013,6 +89184,15 @@ var PermissionManager = class {
 		const { signal } = context;
 		const id = context.toolCall.id;
 		const name = context.toolCall.name;
+		const turnIdNumber = Number(context.turnId);
+		if (this.approvalTimeoutTurnId !== turnIdNumber) {
+			this.approvalTimeoutTurnId = turnIdNumber;
+			this.approvalTimeoutTools.clear();
+		}
+		if (this.approvalTimeoutTools.has(name)) return this.permissionPolicyResolutionToPrepare({
+			kind: "deny",
+			message: `Approval for ${name} already timed out earlier in this turn — the user is away. Do not re-issue this call; use a path that does not need approval, or stop and report the blockage to the user.`
+		}, context, policyName);
 		const display = context.execution.display ?? {
 			kind: "generic",
 			summary: context.execution.description ?? `Approve ${name}`,
@@ -89063,12 +89243,13 @@ var PermissionManager = class {
 				const timeoutPromise = new Promise((_, reject) => {
 					timeoutHandle = setTimeout(() => {
 						timedOut = true;
-						reject(/* @__PURE__ */ new Error(`Approval request timed out after ${String(APPROVAL_TIMEOUT_MS)}ms`));
+						reject(/* @__PURE__ */ new Error(`Approval request timed out after ${String(APPROVAL_TIMEOUT_MS)}ms. The user is likely away: do NOT re-issue this approval-requiring call. Use a path that does not need approval, or stop and report the blockage to the user.`));
 					}, APPROVAL_TIMEOUT_MS);
 				});
 				response = await Promise.race([customPromise, timeoutPromise]);
 			} catch (error) {
 				this.pendingApprovals.delete(approvalId);
+				if (timedOut) this.approvalTimeoutTools.add(name);
 				this.recordDecision(context, {
 					decision: timedOut ? "timeout" : "cancelled",
 					reason: errorText(error)
@@ -99174,6 +99355,57 @@ function abortedToolOutput(toolName, signal) {
 	return `Tool "${toolName}" was aborted`;
 }
 /**
+* Stringify an `AbortSignal`'s reason for the `abortReason` field.
+*
+* The abort's own words are reported as-is: a signal aborted without an
+* explicit reason carries the runtime's default reason, and that is what the
+* consumer sees rather than a second-hand guess. A signal that was never
+* aborted (`reason === undefined`) and an Error with neither message nor name
+* yield nothing, so the field is omitted instead of recorded blank.
+*/
+function abortReasonText(signal) {
+	const reason = signal.reason;
+	if (reason === void 0 || reason === null) return void 0;
+	if (reason instanceof Error) return nonEmpty(reason.message) ?? nonEmpty(reason.name);
+	if (typeof reason === "string") return nonEmpty(reason);
+	if (typeof reason === "number" || typeof reason === "boolean" || typeof reason === "bigint") return String(reason);
+}
+/** Trimmed text, or undefined when there is nothing to report. */
+function nonEmpty(text) {
+	const trimmed = text.trim();
+	return trimmed.length > 0 ? trimmed : void 0;
+}
+/**
+* Tag a tool's *own* error result as an abort when this step's signal is what
+* cut the call short.
+*
+* Everything the loop synthesizes itself already carries a `code`, but a tool
+* that handles its own interruption returns a plain error result: Bash and
+* Python report an interrupted command through `builder.error(...)`, which
+* only takes the human-readable text. An error result with no code reads as an
+* ordinary failure to the consecutive-failure breaker, so an interrupted
+* command used to charge the streak and (at the stop threshold) end the turn
+* reporting "N consecutive tool calls have failed" — blaming the model for the
+* user's or parent agent's own interrupt.
+*
+* Only the missing case is filled in:
+*   - a result that already carries a code keeps it: the tool's own
+*     classification (`blocked`, `failed`) is more specific than ours;
+*   - a result that is not an error is left untouched: a tool that finished
+*     successfully inside the abort race did succeed.
+*/
+function tagAbortedToolResult(result, signal) {
+	if (!signal.aborted) return result;
+	if (result.isError !== true) return result;
+	if (result.code !== void 0) return result;
+	const abortReason = abortReasonText(signal);
+	return {
+		...result,
+		code: "aborted",
+		...abortReason !== void 0 ? { abortReason } : {}
+	};
+}
+/**
 * Record tool calls that arrived in a truncated response (max_tokens,
 * paused, unknown) but were never executed. Each call gets a `tool.call`
 * event immediately followed by a synthetic `tool.result` with an error
@@ -99260,11 +99492,11 @@ async function runToolCallBatch(step, response) {
 			try {
 				if (effectiveStep.signal.aborted) {
 					await dispatchToolCall(step, call, call.args);
-					pendingResults.push(Promise.resolve(makeErrorToolResult(call, call.args, abortedToolOutput(call.toolName, effectiveStep.signal))));
+					pendingResults.push(Promise.resolve(makeErrorToolResult(call, call.args, abortedToolOutput(call.toolName, effectiveStep.signal), "aborted", abortReasonText(effectiveStep.signal))));
 					continue;
 				}
 				const prepared = await prepareToolCall(effectiveStep, call);
-				pendingResults.push(scheduler.add(prepared.task).catch((error) => makeErrorToolResult(call, call.args, errorMessage$5(error))));
+				pendingResults.push(scheduler.add(prepared.task).catch((error) => synthesizePreparationError(effectiveStep.signal, call, call.args, error, errorMessage$5(error))));
 				if (prepared.stopBatchAfterThis === true) {
 					stopTurn = true;
 					for (const skippedCall of calls.slice(index + 1)) try {
@@ -99286,7 +99518,7 @@ async function runToolCallBatch(step, response) {
 					toolName: call.toolName,
 					error
 				});
-				pendingResults.push(Promise.resolve(makeErrorToolResult(call, call.args, `Tool preparation failed: ${errorMessage$5(error)}`)));
+				pendingResults.push(Promise.resolve(synthesizePreparationError(effectiveStep.signal, call, call.args, error, `Tool preparation failed: ${errorMessage$5(error)}`)));
 			}
 		}
 		for (const pendingResult of pendingResults) {
@@ -99440,9 +99672,9 @@ function validateExecutableToolArgs(tool, args) {
 	return validateToolArgs(validator, args);
 }
 async function prepareToolCall(step, call) {
-	const settleError = async (args, output, displayFields) => {
+	const settleError = async (args, output, classification, displayFields) => {
 		await dispatchToolCall(step, call, args, displayFields);
-		return { task: makeResolvedToolCallTask(makeErrorToolResult(call, args, output)) };
+		return { task: makeResolvedToolCallTask(makeErrorToolResult(call, args, output, classification?.code, classification?.abortReason)) };
 	};
 	const settleSynthetic = async (args, result, displayFields) => {
 		const coerced = coerceToolResult(result, call.toolName);
@@ -99469,7 +99701,11 @@ async function prepareToolCall(step, call) {
 		return settleError(call.args, output);
 	}
 	const decision = await runPrepareToolExecutionHook(step, call);
-	if (decision.kind === "blocked" || decision.kind === "hookFailed") return settleError(decision.args, decision.output);
+	if (decision.kind === "blocked") return settleError(decision.args, decision.output, { code: "blocked" });
+	if (decision.kind === "hookFailed") return step.signal.aborted ? settleError(decision.args, decision.output, {
+		code: "aborted",
+		abortReason: abortReasonText(step.signal)
+	}) : settleError(decision.args, decision.output);
 	if (decision.kind === "synthetic") return settleSynthetic(decision.args, decision.result);
 	const validationError = validateExecutableToolArgs(call.tool, decision.args);
 	if (validationError !== null) return settleError(decision.args, `Invalid args for tool "${call.toolName}" after prepareToolExecution hook: ${validationError}`);
@@ -99486,12 +99722,15 @@ async function prepareToolCall(step, call) {
 		return settleError(effectiveArgs, error instanceof PathSecurityError ? error.message : `Tool "${call.toolName}" failed to resolve execution: ${errorMessage$5(error)}`);
 	}
 	const displayFields = toolCallDisplayFieldsFromExecution(execution);
-	const settleAborted = () => settleError(effectiveArgs, abortedToolOutput(call.toolName, step.signal), displayFields);
+	const settleAborted = () => settleError(effectiveArgs, abortedToolOutput(call.toolName, step.signal), {
+		code: "aborted",
+		abortReason: abortReasonText(step.signal)
+	}, displayFields);
 	if (step.signal.aborted) return settleAborted();
 	if (execution.isError === true) return settleSynthetic(effectiveArgs, execution, displayFields);
 	const authorization = await runAuthorizeToolExecutionHook(step, call, effectiveArgs, execution);
 	if (step.signal.aborted) return settleAborted();
-	if (authorization?.block === true) return settleError(effectiveArgs, authorization.reason ?? `Tool call "${call.toolName}" was blocked`, displayFields);
+	if (authorization?.block === true) return settleError(effectiveArgs, authorization.reason ?? `Tool call "${call.toolName}" was blocked`, { code: "blocked" }, displayFields);
 	if (authorization?.syntheticResult !== void 0) return settleSynthetic(effectiveArgs, authorization.syntheticResult, displayFields);
 	const executionMetadata = authorization?.executionMetadata ?? decision.metadata;
 	await dispatchToolCall(step, call, effectiveArgs, displayFields);
@@ -99601,20 +99840,22 @@ function toolCallDisplayFieldsFromExecution(execution) {
 async function runRunnableToolCall(step, call, effectiveArgs, metadata, execution) {
 	const { signal } = step;
 	const { toolCall, toolName } = call;
-	if (signal.aborted) return makeErrorToolResult(call, effectiveArgs, abortedToolOutput(toolName, signal));
+	if (signal.aborted) return makeErrorToolResult(call, effectiveArgs, abortedToolOutput(toolName, signal), "aborted", abortReasonText(signal));
 	let toolResult;
 	try {
 		toolResult = coerceToolResult(await executeTool(step, execution, toolCall, toolName, metadata), toolName);
 	} catch (error) {
-		const aborted = isAbortError$1(error) || signal.aborted;
-		if (!aborted) step.log?.warn("tool execution failed", {
-			toolName,
-			toolCallId: toolCall.id,
-			error
-		});
-		return makeErrorToolResult(call, effectiveArgs, aborted ? abortedToolOutput(toolName, signal) : `Tool "${toolName}" failed: ${errorMessage$5(error)}`);
+		if (!(isAbortError$1(error) || signal.aborted)) {
+			step.log?.warn("tool execution failed", {
+				toolName,
+				toolCallId: toolCall.id,
+				error
+			});
+			return makeErrorToolResult(call, effectiveArgs, `Tool "${toolName}" failed: ${errorMessage$5(error)}`, "failed");
+		}
+		return makeErrorToolResult(call, effectiveArgs, abortedToolOutput(toolName, signal), "aborted", abortReasonText(signal));
 	}
-	return makeToolResult(call, effectiveArgs, toolResult);
+	return makeToolResult(call, effectiveArgs, tagAbortedToolResult(toolResult, signal));
 }
 async function finalizePendingToolResult(step, pendingResult) {
 	const { hooks, signal, turnId, currentStep, llm } = step;
@@ -99646,12 +99887,15 @@ async function finalizePendingToolResult(step, pendingResult) {
 			error
 		});
 		const output = aborted ? `Tool "${pendingResult.toolName}" aborted during finalizeToolResult hook.` : `finalizeToolResult hook failed for "${pendingResult.toolName}": ${errorMessage$5(error)}`;
+		const abortReason = aborted ? abortReasonText(signal) : void 0;
 		return {
 			...pendingResult,
 			stopTurn: pendingResult.stopTurn,
 			result: {
 				output,
-				isError: true
+				isError: true,
+				...aborted ? { code: "aborted" } : {},
+				...abortReason !== void 0 ? { abortReason } : {}
 			}
 		};
 	}
@@ -99684,9 +99928,12 @@ async function raceExecuteWithGraceTimeout(executePromise, signal, toolName) {
 	const graceSentinel = new Promise((resolve) => {
 		const armTimer = () => {
 			graceTimer = setTimeout(() => {
+				const abortReason = abortReasonText(signal);
 				resolve({
 					output: `Tool "${toolName}" aborted by grace timeout (${String(GRACE_TIMEOUT_MS)}ms)`,
-					isError: true
+					isError: true,
+					code: "aborted",
+					...abortReason !== void 0 ? { abortReason } : {}
 				});
 			}, GRACE_TIMEOUT_MS);
 		};
@@ -99746,12 +99993,18 @@ function normalizeToolResult(r) {
 	const nestedCalls = r.isError === true ? void 0 : r.nestedCalls;
 	const nested = nestedCalls !== void 0 ? { nestedCalls } : {};
 	const messagePart = r.message !== void 0 ? { message: r.message } : {};
-	if (r.isError === true) return {
-		output,
-		isError: true,
-		...nested,
-		...messagePart
-	};
+	if (r.isError === true) {
+		const codePart = r.code !== void 0 ? { code: r.code } : {};
+		const abortReasonPart = r.abortReason !== void 0 ? { abortReason: r.abortReason } : {};
+		return {
+			output,
+			isError: true,
+			...nested,
+			...messagePart,
+			...codePart,
+			...abortReasonPart
+		};
+	}
 	const useless = r.useless;
 	const uselessPart = useless !== void 0 ? { useless } : {};
 	const displayPart = r.display !== void 0 ? { display: r.display } : {};
@@ -99775,10 +100028,32 @@ function makeToolResult(call, args, result) {
 function toolResultStopsTurn(result) {
 	return "stopTurn" in result && result.stopTurn === true;
 }
-function makeErrorToolResult(call, args, output) {
+/**
+* Build an error result for a call the loop settled itself (aborted, failed,
+* blocked, or never run). `code` carries the machine-readable classification
+* and `abortReason` the abort's own attribution — both optional, because a
+* tool's own error result and records written before these fields existed
+* have neither.
+*/
+/**
+* Fallback result for a task or preparation that threw before the tool could
+* author its own failure. A throw inside an interrupt window is not a tool
+* failure: without the `aborted` stamp `classifyToolResult` would count it
+* towards the stop-loss streak and attribute a user or parent interruption to
+* the model. Non-abort failures keep the historical shape (no `code` field),
+* so classification is unchanged, and the emitted message is passed through
+* untouched.
+*/
+function synthesizePreparationError(signal, call, args, error, output) {
+	if (isAbortError$1(error) || signal.aborted) return makeErrorToolResult(call, args, output, "aborted", abortReasonText(signal));
+	return makeErrorToolResult(call, args, output);
+}
+function makeErrorToolResult(call, args, output, code, abortReason) {
 	return makeToolResult(call, args, {
 		output,
-		isError: true
+		isError: true,
+		...code !== void 0 ? { code } : {},
+		...abortReason !== void 0 ? { abortReason } : {}
 	});
 }
 /**
@@ -99859,13 +100134,14 @@ async function executeNestedToolCall(step, parentToolName, request) {
 * does not lose model usage that was already spent.
 */
 async function executeLoopStep(deps) {
-	const { turnId, signal, buildMessages, dispatchEvent, llm, tools, buildTools, hooks, log, currentStep, maxRetryAttempts, recordUsage, mediaProjection } = deps;
+	const { turnId, signal, buildMessages, dispatchEvent, llm, tools, buildTools, hooks, log, currentStep, finalStep, maxRetryAttempts, recordUsage, mediaProjection } = deps;
 	if (hooks?.beforeStep !== void 0) {
 		const beforeStep = await hooks.beforeStep({
 			turnId,
 			stepNumber: currentStep,
 			signal,
-			llm
+			llm,
+			finalStep
 		});
 		if (beforeStep?.block === true) throw new Error(beforeStep.reason ?? `Step ${String(currentStep)} was blocked`);
 	}
@@ -100009,7 +100285,8 @@ async function executeLoopStep(deps) {
 			usage,
 			stopReason: effectiveStopReason,
 			signal,
-			llm
+			llm,
+			finalStep
 		});
 		stopTurnAfterStep = stopTurnAfterStep || afterStep?.stopTurn === true;
 	} catch {}
@@ -100189,9 +100466,10 @@ function createChatStreamingCallbacks(deps) {
 /**
 * Turn-level loop for a stateless agent run.
 *
-* Owns convergence across steps: abort checks at loop boundaries, max-step
-* enforcement, usage aggregation, optional continuation after non-tool stops,
-* and final `TurnResult` mapping. One-step execution lives in `turn-step.ts`.
+* Owns convergence across steps: abort checks at loop boundaries, the
+* max-step budget with its single wrap-up step, usage aggregation, optional
+* continuation after non-tool stops, and final `TurnResult` mapping.
+* One-step execution lives in `turn-step.ts`.
 */
 /**
 * Consecutive steps whose tool calls were ALL rejected during preflight
@@ -100207,6 +100485,9 @@ async function runTurn(input) {
 	let usage = emptyUsage();
 	let steps = 0;
 	let consecutiveRejectedSteps = 0;
+	const stepLimit = maxSteps !== void 0 && maxSteps > 0 ? maxSteps : void 0;
+	let wrapUpIssued = false;
+	let stepBudgetExhausted = false;
 	let stopReason = "end_turn";
 	let activeStep;
 	const mediaProjection = { mode: "normal" };
@@ -100217,7 +100498,16 @@ async function runTurn(input) {
 	try {
 		while (true) {
 			signal.throwIfAborted();
-			if (maxSteps !== void 0 && maxSteps > 0 && steps >= maxSteps) throw createMaxStepsExceededError(maxSteps);
+			let finalStep = false;
+			if (stepLimit !== void 0 && steps >= stepLimit) {
+				if (wrapUpIssued) {
+					stopReason = "end_turn";
+					break;
+				}
+				wrapUpIssued = true;
+				finalStep = true;
+				stepBudgetExhausted = true;
+			}
 			steps += 1;
 			activeStep = steps;
 			const stepResult = await executeLoopStep({
@@ -100231,6 +100521,7 @@ async function runTurn(input) {
 				hooks,
 				log,
 				currentStep: steps,
+				finalStep,
 				maxRetryAttempts,
 				recordUsage: recordStepUsage,
 				hasPendingSteer: input.hasPendingSteer,
@@ -100239,6 +100530,10 @@ async function runTurn(input) {
 				onStreamingDraft: input.onStreamingDraft
 			});
 			activeStep = void 0;
+			if (finalStep) {
+				stopReason = "end_turn";
+				break;
+			}
 			if (stepResult.totalCalls > 0) {
 				if (stepResult.rejectedCalls === stepResult.totalCalls) consecutiveRejectedSteps += 1;
 				else consecutiveRejectedSteps = 0;
@@ -100269,22 +100564,34 @@ async function runTurn(input) {
 				usage
 			};
 		}
-		dispatchEvent(makeInterruptedEvent(isMaxStepsExceededError(error) ? "max_steps" : "error", steps, activeStep, errorMessage$5(error)));
+		dispatchEvent(makeInterruptedEvent("error", steps, activeStep, errorMessage$5(error), turnErrorCode(error)));
 		throw error;
 	}
 	return {
 		stopReason,
 		steps,
-		usage
+		usage,
+		...stepBudgetExhausted ? { stepBudgetExhausted: true } : {}
 	};
 }
-function makeInterruptedEvent(reason, attemptedSteps, activeStep, message) {
+/**
+* Error-protocol classification of the failure that interrupted the turn,
+* when the protocol has one. Unrecognized errors (`internal` by default) are
+* left uncoded so consumers keep their own generic wording instead of
+* printing an "internal error" label for an unclassified throw.
+*/
+function turnErrorCode(error) {
+	if (isScreamError(error)) return error.code;
+	return error instanceof ChatProviderError ? toScreamErrorPayload(error).code : void 0;
+}
+function makeInterruptedEvent(reason, attemptedSteps, activeStep, message, errorCode) {
 	return {
 		type: "turn.interrupted",
 		reason,
 		attemptedSteps,
 		...activeStep !== void 0 ? { activeStep } : {},
-		...message !== void 0 ? { message } : {}
+		...message !== void 0 ? { message } : {},
+		...errorCode !== void 0 ? { errorCode } : {}
 	};
 }
 //#endregion
@@ -103964,7 +104271,8 @@ function toMcpToolDefinition(tool) {
 	return {
 		name: tool.name,
 		description: tool.description ?? "",
-		inputSchema: tool.inputSchema
+		inputSchema: tool.inputSchema,
+		...tool.annotations === void 0 ? {} : { annotations: tool.annotations }
 	};
 }
 /**
@@ -104812,6 +105120,10 @@ var ToolManager = class {
 	trippedPlugins = /* @__PURE__ */ new Set();
 	mcpTools = /* @__PURE__ */ new Map();
 	/** server name → list of qualified tool names registered for that server. */
+	/** Withheld-until-enabled MCP tool names (see registerMcpServer). */
+	deferredMcpTools = /* @__PURE__ */ new Set();
+	/** Deferred MCP tools enabled this session via DiscoverMcpTools. */
+	enabledDeferredMcpTools = /* @__PURE__ */ new Set();
 	mcpToolsByServer = /* @__PURE__ */ new Map();
 	enabledTools = /* @__PURE__ */ new Set();
 	/** Glob patterns (e.g. `mcp__*`, `mcp__github__*`) gating which MCP tools the profile exposes. */
@@ -105110,6 +105422,7 @@ var ToolManager = class {
 			qualifiedNames.push(qualified);
 		}
 		this.mcpToolsByServer.set(serverName, qualifiedNames);
+		if (options?.deferAll === true) for (const qualified of qualifiedNames) this.deferredMcpTools.add(qualified);
 		return {
 			registered: qualifiedNames,
 			collisions
@@ -105118,7 +105431,11 @@ var ToolManager = class {
 	unregisterMcpServer(serverName) {
 		const existing = this.mcpToolsByServer.get(serverName);
 		if (existing === void 0) return false;
-		for (const qualified of existing) this.mcpTools.delete(qualified);
+		for (const qualified of existing) {
+			this.mcpTools.delete(qualified);
+			this.deferredMcpTools.delete(qualified);
+			this.enabledDeferredMcpTools.delete(qualified);
+		}
 		this.mcpToolsByServer.delete(serverName);
 		return true;
 	}
@@ -105175,7 +105492,10 @@ var ToolManager = class {
 	registerConnectedMcpServer(mcp, entry) {
 		const resolved = mcp.resolved(entry.name);
 		if (resolved === void 0) return;
-		const result = this.registerMcpServer(entry.name, resolved.client, resolved.tools, resolved.enabledNames, { mcp });
+		const result = this.registerMcpServer(entry.name, resolved.client, resolved.tools, resolved.enabledNames, {
+			mcp,
+			deferAll: entry.exposure !== "always"
+		});
 		this.emitMcpToolCollisions(entry.name, result.collisions);
 		this.agent.emitEvent({
 			type: "tool.list.updated",
@@ -105211,6 +105531,47 @@ var ToolManager = class {
 	isMcpToolEnabled(name) {
 		return this.mcpAccessPatterns.some((pattern) => import_picomatch.default.isMatch(name, pattern));
 	}
+	/**
+	* True while a tool's schema is withheld from the offered table: the
+	* owning server deferred it and this session has not enabled it yet.
+	*/
+	isDeferredMcpTool(name) {
+		return this.deferredMcpTools.has(name) && !this.enabledDeferredMcpTools.has(name);
+	}
+	/**
+	* Deferred MCP tools the model can ask for: registered, accessible under
+	* the active patterns, but not declared yet. Optionally narrowed to one
+	* server. Sorted by qualified name for stable output.
+	*/
+	listDeferredMcpTools(server) {
+		return [...this.mcpTools.entries()].filter(([name]) => this.isDeferredMcpTool(name) && this.isMcpToolEnabled(name)).filter(([, entry]) => server === void 0 || entry.serverName === server).map(([name, entry]) => ({
+			name,
+			serverName: entry.serverName,
+			description: entry.tool.description
+		})).toSorted((a, b) => a.name.localeCompare(b.name));
+	}
+	/**
+	* Enable deferred MCP tools for this session (the `DiscoverMcpTools`
+	* tool). Enabled tools join the offered table from the next step on.
+	* Already-enabled, unknown, or pattern-excluded names land in `skipped`
+	* so the caller can report exactly what happened instead of guessing.
+	*/
+	enableDeferredMcpTools(names) {
+		const enabled = [];
+		const skipped = [];
+		for (const name of names) {
+			if (!this.deferredMcpTools.has(name) || this.enabledDeferredMcpTools.has(name) || !this.isMcpToolEnabled(name)) {
+				skipped.push(name);
+				continue;
+			}
+			this.enabledDeferredMcpTools.add(name);
+			enabled.push(name);
+		}
+		return {
+			enabled,
+			skipped
+		};
+	}
 	/** The enabled-name filter a turn freezes at its start. */
 	snapshotEnabledTools() {
 		return {
@@ -105227,7 +105588,7 @@ var ToolManager = class {
 	* shows up on the very next step.
 	*/
 	loopToolsFor(filter) {
-		const mcpNames = [...this.mcpTools.keys()].filter((name) => filter.mcpPatterns.some((pattern) => import_picomatch.default.isMatch(name, pattern)));
+		const mcpNames = [...this.mcpTools.keys()].filter((name) => filter.mcpPatterns.some((pattern) => import_picomatch.default.isMatch(name, pattern)) && !this.isDeferredMcpTool(name));
 		const hideGoalMutationTools = this.agent.goal.getGoal().goal === null;
 		const tools = uniq([...filter.names, ...mcpNames]).toSorted((a, b) => a.localeCompare(b)).filter((name) => !(hideGoalMutationTools && (name === "SetGoalBudget" || name === "UpdateGoal" || name === "WriteGoalNote"))).map((name) => this.userTools.get(name) ?? this.mcpTools.get(name)?.tool ?? this.builtinTools.get(name)).filter((tool) => !!tool);
 		return this.decorateScriptOffering(tools);
@@ -105262,7 +105623,7 @@ var ToolManager = class {
 		for (const entry of this.mcpTools.values()) yield {
 			name: entry.tool.name,
 			description: entry.tool.description,
-			active: this.isMcpToolEnabled(entry.tool.name),
+			active: this.isMcpToolEnabled(entry.tool.name) && !this.isDeferredMcpTool(entry.tool.name),
 			source: "mcp"
 		};
 	}
@@ -105320,6 +105681,7 @@ var ToolManager = class {
 			this.agent.cron && new CronCreateTool(this.agent.cron),
 			this.agent.cron && new CronListTool(this.agent.cron),
 			this.agent.cron && new CronDeleteTool(this.agent.cron),
+			this.agent.mcp && new DiscoverMcpToolsTool(this),
 			this.agent.type === "main" && new CreateGoalTool(this.agent),
 			this.agent.type === "main" && new UpdateGoalTool(this.agent, createGoalGrader(this.agent)),
 			this.agent.type === "main" && new GetGoalTool(this.agent),
@@ -105384,6 +105746,77 @@ var ToolManager = class {
 	}
 };
 //#endregion
+//#region ../../packages/agent-core/src/agent/turn/defaults.ts
+/**
+* Centralized tunables for turn orchestration (`agent/turn`).
+*
+* Every threshold that shapes turn behavior lives here with a one-line
+* rationale, so tuning a turn is a single-file edit instead of a hunt across
+* `turn/index.ts` and friends. Values are referenced from the orchestration
+* code; keep this file the source of truth.
+*
+* Related thresholds outside this module (kept where they live because they
+* belong to other layers):
+* - compaction: `agent/compaction/micro.ts` (0.3, 1.15), `agent/compaction/strategy.ts` (0.85/0.9, 2.5)
+* - retry: `loop/retry.ts` (10 attempts, 0.5s→32s ±25%)
+* - steer polling: `loop/tool-call.ts` (150ms)
+* - step limits: `loop/run-turn.ts` (8 consecutive rejected steps); the
+*   default per-turn step budget lives here (`maxStepsPerTurn`)
+* - tool output truncation: `agent/context/index.ts` (5000 tokens), `tools/support/result-builder.ts` (50KB)
+*/
+const TURN_DEFAULTS = {
+	/**
+	* Convergence gate: max times the turn injects a `<system-reminder>` to
+	* force continuation (empty step, non-exploratory tool failure, failed
+	* verification) — all `correction`-category reasons in the stop gate's
+	* three-category scheme (`correction` / `external-input` / `quality-floor`;
+	* see 「续轮输出纪律」 in `docs/turn-pipeline.md`). Bounded so a model that
+	* can't converge ends the turn instead of looping forever. Internal state
+	* upkeep (checklist bookkeeping, goal progress, summary polish) is never a
+	* reason: those reminders run before the answer, never as a post-answer
+	* continuation.
+	*/
+	maxConvergenceInjections: 3,
+	/**
+	* Final response length below which a reply counts as "trivial"
+	* (e.g. just "done"). Triggers the summary guard that asks for a
+	* structured deliverability summary before yielding.
+	*/
+	minFinalResponseLength: 60,
+	/**
+	* Goal mode: max continuation turns when the goal has no explicit turn
+	* budget. Prevents a goal from spinning forever and burning tokens.
+	*/
+	maxGoalTurns: 50,
+	/**
+	* Consecutive failed model tool calls that trigger a "change approach"
+	* reminder at the next step boundary.
+	*/
+	toolFailureNoticeStreak: 6,
+	/**
+	* Consecutive failed model tool calls that end the turn: the next step
+	* becomes a final wrap-up in which the model is asked to stop and report.
+	*/
+	toolFailureStopStreak: 10,
+	/**
+	* Default per-turn step budget when `loop_control.max_steps_per_turn` is
+	* unset. **Scope: one single turn** — an autonomous run with no user
+	* participation (each new user message starts a fresh budget). 160 leaves
+	* headroom for long, script-driven workflows; a lower bound was cutting
+	* legitimate big-script runs off. Reaching it is not a failure: the loop
+	* runs one extra wrap-up step that tells the model to stop and report to
+	* the user, then ends the turn. Set `max_steps_per_turn = 0` to disable
+	* the budget.
+	*/
+	maxStepsPerTurn: 160
+};
+//#endregion
+//#region ../../packages/agent-core/src/agent/turn/tool-failure-streak.ts
+function classifyToolResult(result) {
+	if (result.isError === true) return result.code === "aborted" ? "neutral" : "failure";
+	return "success";
+}
+//#endregion
 //#region ../../packages/agent-core/src/agent/turn/goal.ts
 const GOAL_CONTINUATION_PROMPT = [
 	"Continue working toward the active goal.",
@@ -105461,7 +105894,8 @@ function mapLoopEvent(event, turnId) {
 			delayMs: event.delayMs,
 			errorName: event.errorName,
 			errorMessage: event.errorMessage,
-			statusCode: event.statusCode
+			statusCode: event.statusCode,
+			errorCode: event.errorCode
 		};
 		case "content.part": return;
 		case "tool.call": return {
@@ -105481,7 +105915,9 @@ function mapLoopEvent(event, turnId) {
 			isError: event.result.isError,
 			display: event.result.isError === true ? void 0 : event.result.display,
 			message: event.result.message,
-			nestedCalls: event.result.isError === true ? void 0 : event.result.nestedCalls
+			nestedCalls: event.result.isError === true ? void 0 : event.result.nestedCalls,
+			code: event.result.isError === true ? event.result.code : void 0,
+			abortReason: event.result.isError === true ? event.result.abortReason : void 0
 		};
 		case "turn.interrupted":
 			if (event.activeStep === void 0) return void 0;
@@ -105490,7 +105926,8 @@ function mapLoopEvent(event, turnId) {
 				turnId,
 				step: event.activeStep,
 				reason: event.reason,
-				message: event.message
+				message: event.message,
+				errorCode: event.errorCode
 			};
 		case "text.delta": return {
 			type: "assistant.delta",
@@ -105854,49 +106291,6 @@ var ToolCallDeduplicator = class {
 	}
 };
 //#endregion
-//#region ../../packages/agent-core/src/agent/turn/defaults.ts
-/**
-* Centralized tunables for turn orchestration (`agent/turn`).
-*
-* Every threshold that shapes turn behavior lives here with a one-line
-* rationale, so tuning a turn is a single-file edit instead of a hunt across
-* `turn/index.ts` and friends. Values are referenced from the orchestration
-* code; keep this file the source of truth.
-*
-* Related thresholds outside this module (kept where they live because they
-* belong to other layers):
-* - compaction: `agent/compaction/micro.ts` (0.3, 1.15), `agent/compaction/strategy.ts` (0.85/0.9, 2.5)
-* - retry: `loop/retry.ts` (10 attempts, 0.5s→32s ±25%)
-* - steer polling: `loop/tool-call.ts` (150ms)
-* - step limits: `loop/run-turn.ts` (maxSteps, 8 consecutive rejected steps)
-* - tool output truncation: `agent/context/index.ts` (5000 tokens), `tools/support/result-builder.ts` (50KB)
-*/
-const TURN_DEFAULTS = {
-	/**
-	* Convergence gate: max times the turn injects a `<system-reminder>` to
-	* force continuation (empty step, non-exploratory tool failure, failed
-	* verification) — all `correction`-category reasons in the stop gate's
-	* three-category scheme (`correction` / `external-input` / `quality-floor`;
-	* see 「续轮输出纪律」 in `docs/turn-pipeline.md`). Bounded so a model that
-	* can't converge ends the turn instead of looping forever. Internal state
-	* upkeep (checklist bookkeeping, goal progress, summary polish) is never a
-	* reason: those reminders run before the answer, never as a post-answer
-	* continuation.
-	*/
-	maxConvergenceInjections: 3,
-	/**
-	* Final response length below which a reply counts as "trivial"
-	* (e.g. just "done"). Triggers the summary guard that asks for a
-	* structured deliverability summary before yielding.
-	*/
-	minFinalResponseLength: 60,
-	/**
-	* Goal mode: max continuation turns when the goal has no explicit turn
-	* budget. Prevents a goal from spinning forever and burning tokens.
-	*/
-	maxGoalTurns: 50
-};
-//#endregion
 //#region ../../packages/agent-core/src/agent/turn/index.ts
 /** Cap on how long the first turn waits for MCP servers to finish loading. */
 const MCP_WAIT_TIMEOUT_MS = 1e4;
@@ -105929,6 +106323,26 @@ var TurnFlow = class {
 	convergenceInjections = 0;
 	currentStepHadContent = false;
 	lastToolFailure = null;
+	/**
+	* Consecutive-failure circuit breaker (model-issued calls only; nested
+	* calls are excluded): `toolFailureStreak` counts consecutive `isError`
+	* results and resets on any success. Crossing the notice threshold queues a
+	* "change approach" reminder; crossing the stop threshold makes the next
+	* step a wrap-up after which the turn ends. Injections happen at the next
+	* step boundary (beforeStep), never mid-batch.
+	*/
+	toolFailureStreak = 0;
+	toolFailureNoticeIssued = false;
+	toolFailureNoticePending = false;
+	toolFailureWrapUpPending = false;
+	/** Set once the wrap-up step for the failure stop threshold ran. */
+	failureStopEngaged = false;
+	/**
+	* True when this turn's loop result carried `stepBudgetExhausted` (the
+	* wrap-up step after the step budget ran out). Reset per turn; read when
+	* `turn.ended` is built so hosts can distinguish a budget cut.
+	*/
+	stepBudgetExhaustedThisTurn = false;
 	summaryGuardInjected = false;
 	turnStartWorkingSetPathCount = 0;
 	turnStartVerificationCount = 0;
@@ -106184,6 +106598,12 @@ var TurnFlow = class {
 		this.convergenceInjections = 0;
 		this.currentStepHadContent = false;
 		this.lastToolFailure = null;
+		this.toolFailureStreak = 0;
+		this.toolFailureNoticeIssued = false;
+		this.toolFailureNoticePending = false;
+		this.toolFailureWrapUpPending = false;
+		this.failureStopEngaged = false;
+		this.stepBudgetExhaustedThisTurn = false;
 		this.currentTurnId = turnId;
 		this.agent.workingSet.decay(turnId);
 		this.summaryGuardInjected = false;
@@ -106214,7 +106634,8 @@ var TurnFlow = class {
 				ended = {
 					type: "turn.ended",
 					turnId,
-					reason: stopReason === "aborted" ? "cancelled" : "completed"
+					reason: stopReason === "aborted" ? "cancelled" : "completed",
+					...this.stepBudgetExhaustedThisTurn ? { stepBudgetExhausted: true } : {}
 				};
 			}
 		} catch (error) {
@@ -106329,7 +106750,7 @@ var TurnFlow = class {
 			const model = this.agent.config.model;
 			const loopControl = this.agent.screamConfig?.loopControl;
 			try {
-				return (await runTurn({
+				const result = await runTurn({
 					turnId: String(turnId),
 					signal,
 					llm: this.agent.llm,
@@ -106338,7 +106759,7 @@ var TurnFlow = class {
 					tools: this.agent.tools.loopTools,
 					buildTools: () => stepTools.current = this.agent.tools.loopToolsFor(turnToolFilter),
 					log: this.agent.log,
-					maxSteps: loopControl?.maxStepsPerTurn,
+					maxSteps: loopControl?.maxStepsPerTurn ?? TURN_DEFAULTS.maxStepsPerTurn,
 					maxRetryAttempts: loopControl?.maxRetriesPerStep,
 					hasPendingSteer: () => this.steerBuffer.some(isInterruptingSteer),
 					pendingSteerKind: () => {
@@ -106356,10 +106777,29 @@ var TurnFlow = class {
 						});
 					},
 					hooks: {
-						beforeStep: async ({ signal: stepSignal, stepNumber }) => {
+						beforeStep: async ({ signal: stepSignal, stepNumber, finalStep }) => {
 							this.flushSteerBuffer();
 							this.currentStepHadContent = false;
 							await this.agent.fullCompaction.beforeStep(stepSignal);
+							if (finalStep === true) this.agent.context.appendSystemReminder("Step budget exhausted: this is the final step of this turn. Stop exploring and do not start new work. Report to the user now in a normal text reply — what you completed, what is blocked, what you already tried, and which decision or input you need from them. This report is a normal completion, not a failure.", {
+								kind: "system_trigger",
+								name: "step_budget_exhausted"
+							});
+							if (this.toolFailureNoticePending) {
+								this.toolFailureNoticePending = false;
+								this.agent.context.appendSystemReminder(`${TURN_DEFAULTS.toolFailureNoticeStreak} consecutive tool calls have failed. Re-read the errors and change approach — different parameters, a different tool, or re-check your assumptions. If the blockage needs user input, stop and report it instead of retrying.`, {
+									kind: "system_trigger",
+									name: "tool_failure_streak"
+								});
+							}
+							if (this.toolFailureWrapUpPending) {
+								this.toolFailureWrapUpPending = false;
+								this.failureStopEngaged = true;
+								this.agent.context.appendSystemReminder(`${TURN_DEFAULTS.toolFailureStopStreak} consecutive tool calls have failed. This is the final step of this turn: stop calling tools and report to the user now — what you tried, how the attempts failed, what blocks progress, and what you need from them.`, {
+									kind: "system_trigger",
+									name: "tool_failure_stop"
+								});
+							}
 							const goal = this.agent.goal.getGoal().goal;
 							if (stepNumber === 1 && goal?.status === "active" && !this.todoSeenThisTurn) this.agent.context.appendSystemReminder("This turn is working toward an active goal. You MUST call TodoList to create or update the plan before making changes.", {
 								kind: "system_trigger",
@@ -106397,8 +106837,10 @@ var TurnFlow = class {
 							await this.agent.goal.recordTokenUsage(grandTotal(usage), usage);
 							await this.agent.fullCompaction.afterStep();
 							deduper.endStep();
+							if (this.failureStopEngaged) return { stopTurn: true };
 						},
 						shouldContinueAfterStop: async ({ signal, stopReason }) => {
+							if (this.failureStopEngaged) return { continue: false };
 							if (this.flushSteerBuffer()) return { continue: true };
 							signal.throwIfAborted();
 							if (stopReason === "max_tokens" && !this.maxTokensRecoveryAttempted && this.agent.config.profileName === "agent") {
@@ -106478,6 +106920,20 @@ var TurnFlow = class {
 						finalizeToolResult: async (ctx) => {
 							const finalResult = ctx.nested === true ? ctx.result : await deduper.finalizeResult(ctx.toolCall.id, ctx.toolCall.name, ctx.args, ctx.result);
 							const { isError, output } = finalResult;
+							if (ctx.nested !== true) {
+								const outcome = classifyToolResult(finalResult);
+								if (outcome === "failure") {
+									this.toolFailureStreak += 1;
+									if (this.toolFailureStreak >= TURN_DEFAULTS.toolFailureStopStreak) this.toolFailureWrapUpPending = true;
+									else if (this.toolFailureStreak === TURN_DEFAULTS.toolFailureNoticeStreak && !this.toolFailureNoticeIssued) {
+										this.toolFailureNoticeIssued = true;
+										this.toolFailureNoticePending = true;
+									}
+								} else if (outcome === "success") {
+									this.toolFailureStreak = 0;
+									this.toolFailureNoticeIssued = false;
+								}
+							}
 							this.agent.permission.settlePrivateRead(ctx.toolCall.id, isError === true);
 							this.agent.sessionMemory.recordToolExecution(ctx.toolCall.name, summarizeToolArgs(ctx.args), isError === true, ctx.stepNumber);
 							this.recordWorkingSetPaths(ctx.toolCall.name, ctx.args, Number(ctx.turnId));
@@ -106535,18 +106991,15 @@ var TurnFlow = class {
 							return finalResult;
 						}
 					}
-				})).stopReason;
+				});
+				if (result.stepBudgetExhausted === true) this.stepBudgetExhaustedThisTurn = true;
+				return result.stopReason;
 			} catch (error) {
 				if (isContextOverflowError(error)) {
 					await this.agent.fullCompaction.handleOverflowError(signal, error);
 					continue;
 				}
-				if (isMaxStepsExceededError(error)) this.agent.log.warn("turn hit max steps", {
-					turnId,
-					steps: this.currentStepByTurn.get(turnId) ?? this.currentStep,
-					limit: isScreamError(error) ? error.details?.["maxSteps"] : void 0
-				});
-				else this.agent.log.error("turn failed", {
+				this.agent.log.error("turn failed", {
 					turnId,
 					error
 				});
@@ -108270,6 +108723,7 @@ function permissionRuleToToml(rule) {
 function servicesToToml(services, rawServices) {
 	const out = cloneRecord(rawServices);
 	for (const key of [
+		"google",
 		"duckduckgo",
 		"bing",
 		"sogou",
@@ -111563,6 +112017,25 @@ function assertMcpInputSchema(toolName, inputSchema) {
 }
 //#endregion
 //#region ../../packages/agent-core/src/mcp/connection-manager.ts
+/**
+* Narrow an MCP `annotations` block to the four boolean hints we consume.
+* The block also carries display-only fields (`title`) and the values are
+* author-declared by the server, so anything non-boolean is dropped rather
+* than coerced.
+*/
+function mapMcpAnnotations(raw) {
+	const result = {};
+	for (const key of [
+		"readOnlyHint",
+		"destructiveHint",
+		"idempotentHint",
+		"openWorldHint"
+	]) {
+		const value = raw[key];
+		if (typeof value === "boolean") result[key] = value;
+	}
+	return result;
+}
 const DEFAULT_STARTUP_TIMEOUT_MS = 6e4;
 /** Effective tool-call budget for a server: configured value or the default. */
 function resolveToolCallTimeoutMs(config) {
@@ -111825,7 +112298,8 @@ var McpConnectionManager = class {
 		return (await client.listTools()).map((mcpTool) => ({
 			name: mcpTool.name,
 			description: mcpTool.description,
-			parameters: assertMcpInputSchema(mcpTool.name, mcpTool.inputSchema)
+			parameters: assertMcpInputSchema(mcpTool.name, mcpTool.inputSchema),
+			...mcpTool.annotations === void 0 ? {} : { annotations: mapMcpAnnotations(mcpTool.annotations) }
 		}));
 	}
 	async closeClient(entry) {
@@ -111875,7 +112349,8 @@ function toPublicEntry(entry) {
 		status: entry.status,
 		toolCount: entry.status === "connected" && entry.enabledNames !== void 0 ? entry.enabledNames.size : 0,
 		error: entry.error,
-		capabilities: resolveServerCapabilities(entry.name, entry.config)
+		capabilities: resolveServerCapabilities(entry.name, entry.config),
+		exposure: entry.config.exposure ?? "on-demand"
 	};
 }
 function computeEnabledNames(config, tools) {
@@ -127104,9 +127579,9 @@ function isAnomalyResponse(html) {
 * `<a|div|span class="result__snippet">` sibling for the preview text.
 * Sponsored rows, missing snippets, and the pagination row are tolerated.
 */
-const RESULT_BLOCK_RE$1 = /<div\b[^>]*\bclass="[^"]*\bresult\b[^"]*"[^>]*>([\s\S]*?)(?=<div\b[^>]*\bclass="[^"]*\bresult\b|<div\b[^>]*\bclass="[^"]*\bnav-link\b|$)/g;
-const RESULT_TITLE_RE$1 = /<a\b[^>]*\bclass="[^"]*\bresult__a\b[^"]*"[^>]*\bhref="([^"]+)"[^>]*>([\s\S]*?)<\/a>/;
-const RESULT_SNIPPET_RE$1 = /<(?:a|div|span)\b[^>]*\bclass="[^"]*\bresult__snippet\b[^"]*"[^>]*>([\s\S]*?)<\/(?:a|div|span)>/;
+const RESULT_BLOCK_RE = /<div\b[^>]*\bclass="[^"]*\bresult\b[^"]*"[^>]*>([\s\S]*?)(?=<div\b[^>]*\bclass="[^"]*\bresult\b|<div\b[^>]*\bclass="[^"]*\bnav-link\b|$)/g;
+const RESULT_TITLE_RE = /<a\b[^>]*\bclass="[^"]*\bresult__a\b[^"]*"[^>]*\bhref="([^"]+)"[^>]*>([\s\S]*?)<\/a>/;
+const RESULT_SNIPPET_RE = /<(?:a|div|span)\b[^>]*\bclass="[^"]*\bresult__snippet\b[^"]*"[^>]*>([\s\S]*?)<\/(?:a|div|span)>/;
 /** Strip inline tags (DDG wraps query terms in `<b>`) and decode entities. */
 function decodeHtmlText$2(value) {
 	return value.replaceAll(/<[^>]*>/g, " ").replaceAll(/&#(\d+);/g, (_, code) => String.fromCodePoint(Number(code))).replaceAll(/&#x([0-9a-f]+);/gi, (_, code) => String.fromCodePoint(Number.parseInt(code, 16))).replaceAll(/&nbsp;/gi, " ").replaceAll(/&amp;/gi, "&").replaceAll(/&lt;/gi, "<").replaceAll(/&gt;/gi, ">").replaceAll(/&quot;/gi, "\"").replaceAll(/&#39;|&apos;/gi, "'").replaceAll(/\s+/g, " ").trim();
@@ -127131,16 +127606,16 @@ function unwrapResultUrl(href) {
 function parseHtmlResults(html) {
 	const results = [];
 	const seen = /* @__PURE__ */ new Set();
-	for (const match of html.matchAll(RESULT_BLOCK_RE$1)) {
+	for (const match of html.matchAll(RESULT_BLOCK_RE)) {
 		const block = match[1] ?? "";
-		const title = RESULT_TITLE_RE$1.exec(block);
+		const title = RESULT_TITLE_RE.exec(block);
 		if (title === null) continue;
 		const url = unwrapResultUrl(title[1] ?? "");
 		if (url === void 0 || seen.has(url)) continue;
 		const titleText = decodeHtmlText$2(title[2] ?? "");
 		if (titleText === "") continue;
 		seen.add(url);
-		const snippet = RESULT_SNIPPET_RE$1.exec(block);
+		const snippet = RESULT_SNIPPET_RE.exec(block);
 		const snippetText = snippet !== null ? decodeHtmlText$2(snippet[1] ?? "") : "";
 		results.push({
 			title: titleText,
@@ -127151,12 +127626,12 @@ function parseHtmlResults(html) {
 	return results;
 }
 //#endregion
-//#region ../../packages/agent-core/src/tools/providers/bing-search.ts
-const BING_SEARCH_URL = "https://www.bing.com/search";
-/** Browser-like UA so Bing serves the standard server-rendered page. */
+//#region ../../packages/agent-core/src/tools/providers/google-search.ts
+const GOOGLE_SEARCH_URL = "https://www.google.com/search";
+/** Browser-like UA so Google serves the standard server-rendered page. */
 const BROWSER_USER_AGENT = "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36";
-var BingSearchProvider = class {
-	name = "bing";
+var GoogleSearchProvider = class {
+	name = "google";
 	fetchImpl;
 	constructor(options = {}) {
 		this.fetchImpl = options.fetchImpl ?? globalThis.fetch.bind(globalThis);
@@ -127164,39 +127639,47 @@ var BingSearchProvider = class {
 	async search(query, options) {
 		const limit = options?.limit ?? 5;
 		const params = new URLSearchParams({ q: query });
-		params.set("count", String(Math.min(Math.max(limit + 5, 10), 30)));
-		const response = await this.fetchImpl(`${BING_SEARCH_URL}?${params.toString()}`, {
+		params.set("num", String(Math.min(Math.max(limit + 5, 10), 20)));
+		const response = await this.fetchImpl(`${GOOGLE_SEARCH_URL}?${params.toString()}`, {
 			method: "GET",
 			headers: {
 				Accept: "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8",
 				"Accept-Language": "en,en-US;q=0.9",
-				Referer: "https://www.bing.com/",
+				Referer: "https://www.google.com/",
 				"Upgrade-Insecure-Requests": "1",
 				"User-Agent": BROWSER_USER_AGENT
 			},
 			signal: withHardTimeout(options?.signal)
 		});
 		const html = await response.text();
-		if (!response.ok) throw new Error(`Bing request failed: HTTP ${String(response.status)}`);
-		if (isChallengeResponse(html)) throw new Error("Bing blocked the request with an anti-bot challenge (shared-egress IPs are flagged more often)");
-		return parseBingResults(html).slice(0, limit);
+		if (!response.ok) throw new Error(`Google request failed: HTTP ${String(response.status)}`);
+		if (isChallengeResponse(html)) throw new Error("Google blocked the request with a CAPTCHA/consent interstitial");
+		return parseGoogleResults(html).slice(0, limit);
 	}
 };
 /**
-* Bing answers suspected automation with a challenge interstitial ("One last
-* step…", CAPTCHA or a JS-only gate) that contains no result blocks. The
-* presence of `b_algo` wins over keyword matching (some real result pages
-* embed the word "challenge").
+* Google answers suspected automation with a `/sorry/` CAPTCHA page, an
+* "unusual traffic" wall, or a consent interstitial ("Before you continue
+* to…") — none of which carry organic `<h3>` result links.
 */
 function isChallengeResponse(html) {
-	if (/\bclass="[^"]*\bb_algo\b[^"]*"/.test(html)) return false;
-	return /one last step|captcha|verify (?:you are|it's) (?:a )?human|enable javascript|bm\.php/i.test(html);
-}
-const RESULT_BLOCK_RE = new RegExp(`<li\\b[^>]*\\bclass="[^"]*\\bb_algo\\b[^"]*"[^>]*>[\\s\\S]*?(?=<li\\b[^>]*\\bclass="[^"]*\\bb_algo\\b[^"]*"|<li\\b[^>]*\\bclass="[^"]*\\bb_ans\\b|<\\/ol>|\$)`, "g");
-const RESULT_TITLE_RE = /<h2[^>]*>\s*<a\b[^>]*\bhref="([^"]+)"[^>]*>([\s\S]*?)<\/a>/;
-const RESULT_SNIPPET_RE = /<p\b[^>]*\bclass="b_(?:lineclamp|paractl)[^"]*"[^>]*>([\s\S]*?)<\/p>/;
-/** Strip markup and decode entities. Inline tags (Bing highlights query
-* terms in `<strong>`) are removed WITHOUT a space so punctuation stays
+	return /https?:\/\/(?:www\.)?google\.[a-z.]+\/sorry\/|g-recaptcha|recaptcha|unusual traffic|before you continue to|enable javascript|consent\.google\./i.test(html);
+}
+/**
+* An organic result anchors its `<h3>` title inside the link (`<a href>` →
+* `<h3>`), or wraps the link inside the heading on some variants. Knowledge
+* panels, ad rows and related-question carousels do not pair an external
+* `href` with an `<h3>` and are dropped.
+*/
+const TITLE_BLOCK_RE = /<h3\b[^>]*>([\s\S]*?)<\/h3>/g;
+const WRAPPING_ANCHOR_RE = /<a\b[^>]*\bhref="([^"]+)"[^>]*>\s*$/;
+const INNER_ANCHOR_RE = /<a\b[^>]*\bhref="([^"]+)"/;
+const SNIPPET_RE = /<div\b[^>]*\bclass="[^"]*\b(?:VwiC3b|IsZVec|hgKEbd|aCOpRe)\b[^"]*"[^>]*>([\s\S]*?)<\/div>/;
+/** Hosts that are navigation/ad surface rather than organic results. */
+const SELF_OR_AD_HOST_RE = /https?:\/\/(?:[^/]*\.)?(?:googleadservices\.com|googlesyndication\.com|doubleclick\.net|gstatic\.com)\//i;
+const SELF_NAVIGATING_PATH_RE = /https?:\/\/(?:[^/]*\.)?google(?:adservices|\.[a-z.]+)*\.[a-z.]+\/(?:url|aclk|imgres|search|apps-activity|shop(?:ping)?|images)\b/i;
+/** Strip markup and decode entities. Inline tags (Google highlights query
+* terms in `<em>`/`<b>`) are removed WITHOUT a space so punctuation stays
 * attached; block-ish tags collapse to a space so words do not fuse. */
 function decodeHtmlText$1(value) {
 	return value.replaceAll(/<br\s*\/?\s*>/gi, " ").replaceAll(/<\/(?:p|div|li|h\d)>/gi, " ").replaceAll(/<[^>]*>/g, "").replaceAll(/&#(\d+);/g, (_, code) => {
@@ -127208,43 +127691,49 @@ function decodeHtmlText$1(value) {
 	}).replaceAll("&nbsp;", " ").replaceAll("&amp;", "&").replaceAll("&lt;", "<").replaceAll("&gt;", ">").replaceAll("&quot;", "\"").replaceAll(/&#39;|&apos;/gi, "'").replaceAll(/\s+/g, " ").trim();
 }
 /**
-* Resolve a Bing result href to the underlying target URL. Bing routes
-* outbound clicks through `bing.com/ck/a?…&u=a1<base64url>`; the `u=a1`
-* payload is base64url-encoded. Direct absolute URLs and protocol-relative
-* links are handled as-is.
+* Resolve a Google result href to the underlying target URL. Google routes
+* some organic clicks through `/url?q=<target>&…`; direct absolute URLs and
+* protocol-relative links are handled as-is. The redirect check runs BEFORE
+* the self-navigating filter, since the wrapper URL is self-referential by
+* design while its target is the actual result.
 */
-function unwrapBingUrl(href) {
+const REDIRECT_HOST_RE = /^https?:\/\/[^/]*\bgoogle[a-z.]*\.[a-z.]+\/url\b/i;
+const REDIRECT_TARGET_RE = /[?&]q=([^&]+)/;
+function unwrapGoogleUrl(href) {
 	if (href === "") return void 0;
 	const decoded = href.replaceAll("&amp;", "&");
-	const wrap = /[?&]u=a1([^&]+)/.exec(decoded);
-	if (wrap?.[1] !== void 0) {
-		const base64 = wrap[1].replaceAll("-", "+").replaceAll("_", "/");
-		const padded = base64 + "=".repeat((4 - base64.length % 4) % 4);
+	if (SELF_OR_AD_HOST_RE.test(decoded)) return void 0;
+	if (REDIRECT_HOST_RE.test(decoded)) {
+		const wrapped = REDIRECT_TARGET_RE.exec(decoded)?.[1];
+		if (wrapped === void 0) return void 0;
 		try {
-			const url = Buffer.from(padded, "base64").toString("utf8");
+			const url = decodeURIComponent(wrapped).trim();
 			if (url.startsWith("http://") || url.startsWith("https://")) return url;
 		} catch {
 			return;
 		}
 		return;
 	}
-	if (/^https?:\/\/[^/]*\.?bing\.com\/ck\//i.test(decoded)) return void 0;
+	if (SELF_NAVIGATING_PATH_RE.test(decoded)) return void 0;
 	if (decoded.startsWith("//")) return `https:${decoded}`;
 	if (decoded.startsWith("http://") || decoded.startsWith("https://")) return decoded;
 }
-function parseBingResults(html) {
+function parseGoogleResults(html) {
 	const results = [];
 	const seen = /* @__PURE__ */ new Set();
-	for (const match of html.matchAll(RESULT_BLOCK_RE)) {
-		const block = match[0];
-		const title = RESULT_TITLE_RE.exec(block);
-		if (title === null) continue;
-		const url = unwrapBingUrl(title[1] ?? "");
+	for (const match of html.matchAll(TITLE_BLOCK_RE)) {
+		const headingStart = match.index ?? 0;
+		const headingEnd = headingStart + match[0].length;
+		const inner = match[1] ?? "";
+		let href = WRAPPING_ANCHOR_RE.exec(html.slice(Math.max(0, headingStart - 400), headingStart))?.[1];
+		href ??= INNER_ANCHOR_RE.exec(inner)?.[1];
+		if (href === void 0) continue;
+		const url = unwrapGoogleUrl(href);
 		if (url === void 0 || seen.has(url)) continue;
-		const titleText = decodeHtmlText$1(title[2] ?? "");
+		const titleText = decodeHtmlText$1(inner);
 		if (titleText === "") continue;
 		seen.add(url);
-		const snippet = RESULT_SNIPPET_RE.exec(block);
+		const snippet = SNIPPET_RE.exec(html.slice(headingEnd, headingEnd + 1400));
 		const snippetText = snippet !== null ? decodeHtmlText$1(snippet[1] ?? "") : "";
 		results.push({
 			title: titleText,
@@ -127263,7 +127752,7 @@ const BROWSER_HEADERS = {
 };
 /** Strip inline tags and decode the common named/numeric entities. */
 function decodeHtmlText(value) {
-	return value.replace(/<[^>]*>/g, " ").replace(/&#(\d+);/g, (_, code) => String.fromCharCode(Number(code))).replace(/&#x([0-9a-f]+);/gi, (_, code) => String.fromCharCode(Number.parseInt(code, 16))).replace(/&nbsp;/gi, " ").replace(/&amp;/gi, "&").replace(/&lt;/gi, "<").replace(/&gt;/gi, ">").replace(/&quot;/gi, "\"").replace(/&#39;|&apos;/gi, "'").replace(/\s+/g, " ").trim();
+	return value.replaceAll(/<[^>]*>/g, " ").replaceAll(/&#(\d+);/g, (_, code) => String.fromCodePoint(Number(code))).replaceAll(/&#x([0-9a-f]+);/gi, (_, code) => String.fromCodePoint(Number.parseInt(code, 16))).replaceAll(/&nbsp;/gi, " ").replaceAll(/&amp;/gi, "&").replaceAll(/&lt;/gi, "<").replaceAll(/&gt;/gi, ">").replaceAll(/&quot;/gi, "\"").replaceAll(/&#39;|&apos;/gi, "'").replaceAll(/\s+/g, " ").trim();
 }
 async function searchEngine(spec, fetchImpl, query, options) {
 	const limit = options?.limit ?? 5;
@@ -127281,7 +127770,7 @@ async function searchEngine(spec, fetchImpl, query, options) {
 		const block = match[1] ?? "";
 		const title = spec.titleRe.exec(block);
 		if (title === null) continue;
-		const rawHref = (title[1] ?? "").replace(/&amp;/gi, "&");
+		const rawHref = (title[1] ?? "").replaceAll(/&amp;/gi, "&");
 		const url = spec.normalizeUrl !== void 0 ? spec.normalizeUrl(rawHref) : rawHref;
 		if (url === void 0 || url === "" || seen.has(url)) continue;
 		const titleText = decodeHtmlText(title[2] ?? "");
@@ -130943,8 +131432,8 @@ function buildPaperSearcher() {
 function buildWebSearcher(input) {
 	const services = input.config.services;
 	const providers = [];
+	if (services?.google?.enabled !== false) providers.push(new GoogleSearchProvider());
 	if (services?.duckduckgo?.enabled !== false) providers.push(new DuckDuckGoSearchProvider());
-	if (services?.bing?.enabled !== false) providers.push(new BingSearchProvider());
 	if (services?.sogou?.enabled !== false) providers.push(new SogouSearchProvider());
 	if (services?.baidu?.enabled !== false) providers.push(new BaiduSearchProvider());
 	if (services?.so360?.enabled !== false) providers.push(new So360SearchProvider());
@@ -130961,23 +131450,25 @@ function createSessionId() {
 async function resumeSessionResult(summary, session, warning) {
 	const api = new SessionAPIImpl(session);
 	const agents = {};
-	for (const [agentId, agent] of session.agents) {
+	const main = session.agents.get("main");
+	if (main !== void 0) {
+		const agentId = "main";
 		const config = await api.getConfig({ agentId });
-		const context = await api.getContext({ agentId });
+		const { tokenCount } = await api.getContext({ agentId });
 		const permission = await api.getPermission({ agentId });
 		const plan = await api.getPlan({ agentId });
 		const usage = await api.getUsage({ agentId });
 		agents[agentId] = {
-			type: agent.type,
+			type: main.type,
 			config,
-			context,
-			replay: agent.replayBuilder.buildResult(),
+			context: { tokenCount },
+			replay: main.replayBuilder.buildResult(),
 			permission,
 			plan,
 			usage,
 			tools: await api.getTools({ agentId }),
-			toolStore: agent.tools.storeData(),
-			background: agent.background.list(false)
+			toolStore: main.tools.storeData(),
+			background: main.background.list(false)
 		};
 	}
 	return {
@@ -137101,9 +137592,24 @@ const SPINNER_FRAMES$1 = [
 	"◉"
 ];
 const SPINNER_TICK_MS = 60;
+/**
+* Elapsed suffix for human-blocked states ("等待批准 · 4m"), shown only after a
+* minute: below that a clock reads as noise, while a long silent stall must be
+* visible — the previous behaviour showed nothing ever, which made a stalled
+* approval look like normal work. Units (m/h) are language-neutral symbols, so
+* the suffix is not routed through i18n.
+*/
+function waitingStallSuffix(since) {
+	if (since === null || since === void 0) return "";
+	const seconds = Math.floor((Date.now() - since) / 1e3);
+	if (seconds < 60) return "";
+	const minutes = Math.floor(seconds / 60);
+	if (minutes < 60) return ` · ${String(minutes)}m`;
+	return ` · ${String(Math.floor(minutes / 60))}h${String(minutes % 60)}m`;
+}
 function buildStatusLine(streamingPhase, streamingStartTime, statusFlags) {
-	if (statusFlags.pendingUserAction === "approval") return t("status.awaiting_approval");
-	if (statusFlags.pendingUserAction === "question") return t("status.awaiting_answer");
+	if (statusFlags.pendingUserAction === "approval") return t("status.awaiting_approval") + waitingStallSuffix(statusFlags.pendingUserActionSince);
+	if (statusFlags.pendingUserAction === "question") return t("status.awaiting_answer") + waitingStallSuffix(statusFlags.pendingUserActionSince);
 	if (statusFlags.isCompacting) return t("status.compacting");
 	if (streamingPhase === "idle") return t("status.idle");
 	if (statusFlags.reconnectAttempt > 0) return t("status.reconnecting_short", {
@@ -137291,6 +137797,7 @@ var FooterComponent = class {
 			const statusLine = buildStatusLine(state.streamingPhase, state.streamingStartTime, {
 				isCompacting: state.isCompacting === true,
 				pendingUserAction: state.pendingUserAction ?? null,
+				pendingUserActionSince: state.pendingUserActionSince ?? null,
 				reconnectAttempt: state.reconnectAttempt ?? 0,
 				reconnectMaxAttempts: state.reconnectMaxAttempts
 			});
@@ -138100,6 +138607,13 @@ function buildSessionUsageSection(usage, error, table, value, muted, errorStyle,
 	const subagentTotal = sumTokenRows(subagentRows);
 	const lines = [];
 	lines.push(padName(t("usage.session_total")) + num(sessionTotal.input) + num(sessionTotal.output) + num(sessionTotal.input + sessionTotal.output));
+	let cacheReadTotal = 0;
+	let cacheCreationTotal = 0;
+	for (const [, row] of entries) {
+		cacheReadTotal += usageNumber(row.inputCacheRead);
+		cacheCreationTotal += usageNumber(row.inputCacheCreation);
+	}
+	if (cacheReadTotal > 0 || cacheCreationTotal > 0) lines.push(padName(`  ↳ ${t("usage.cache_rw")}`) + num(cacheReadTotal) + num(cacheCreationTotal));
 	if (subagentRows.length > 0) {
 		const mainInput = Math.max(0, sessionTotal.input - subagentTotal.input);
 		const mainOutput = Math.max(0, sessionTotal.output - subagentTotal.output);
@@ -140078,7 +140592,7 @@ async function guidedGoalSetup(host) {
 		host.showNotice(t("goal.storm_breaker"), t("goal.conflict_loop"));
 		return;
 	}
-	const { TextInputDialogComponent } = await import("./text-input-dialog-BcAJghtL.mjs");
+	const { TextInputDialogComponent } = await import("./text-input-dialog-DWepgNF4.mjs");
 	const initialDesc = await promptText(host, TextInputDialogComponent, {
 		title: t("goal.setup_title_initial"),
 		subtitle: t("goal.setup_desc_hint"),
@@ -140099,7 +140613,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-BcAJghtL.mjs");
+	const { TextInputDialogComponent } = await import("./text-input-dialog-DWepgNF4.mjs");
 	const turnInput = await promptNumber(host, TextInputDialogComponent, {
 		title: t("goal.wizard_title", { objective }),
 		subtitle: t("goal.budget_turns_hint"),
@@ -145183,7 +145697,7 @@ var ToolCallComponent = class ToolCallComponent extends CachedContainer {
 		let bullet;
 		if (isFinished) if (isError) {
 			const output = typeof result?.output === "string" ? result.output : "";
-			bullet = /\b(?:aborted|cancelled|canceled)\b/i.test(output) ? chalk.hex(colors.warning)("⊙ ") : chalk.hex(colors.error)("✗ ");
+			bullet = (result?.code !== void 0 ? result.code === "aborted" : /\b(?:aborted|cancelled|canceled)\b/i.test(output)) ? chalk.hex(colors.warning)("⊙ ") : chalk.hex(colors.error)("✗ ");
 		} else bullet = chalk.hex(colors.success)(STATUS_BULLET);
 		else if (isTruncated) bullet = chalk.hex(colors.error)("✗ ");
 		else bullet = chalk.hex(colors.roleAssistant)(STATUS_BULLET);