chore: fix various typos (#6429)

packages/opencode/src/session/prompt/codex.txt

@@ -240,7 +240,7 @@ You are producing plain text that will later be styled by the CLI. Follow these
 - Choose descriptive names that fit the content
 - Keep headers short (1–3 words) and in `**Title Case**`. Always start headers with `**` and end with `**`
 - Leave no blank line before the first bullet under a header.
-- Section headers should only be used where they genuinely improve scanability; avoid fragmenting the answer.
+- Section headers should only be used where they genuinely improve scannability; avoid fragmenting the answer.
 
 **Bullets**
 
@@ -289,7 +289,7 @@ When referencing files in your response, make sure to include the relevant start
 - Don’t nest bullets or create deep hierarchies.
 - Don’t output ANSI escape codes directly — the CLI renderer applies them.
 - Don’t cram unrelated keywords into a single bullet; split for clarity.
-- Don’t let keyword lists run long — wrap or reformat for scanability.
+- Don’t let keyword lists run long — wrap or reformat for scannability.
 
 Generally, ensure your final answers adapt their shape and depth to the request. For example, answers to code explanations should have a precise, structured explanation with code references that answer the question directly. For tasks with a simple implementation, lead with the outcome and supplement only with what’s needed for clarity. Larger changes can be presented as a logical walkthrough of your approach, grouping related steps, explaining rationale where it adds value, and highlighting next actions to accelerate the user. Your answers should provide the right level of detail while being easily scannable.
 

packages/opencode/src/session/prompt/plan.txt

@@ -12,7 +12,7 @@ is a critical violation. ZERO exceptions.
 
 ## Responsibility
 
-Your current responsibility is to think, read, search, and delegate explore agents to construct a well formed plan that accomplishes the goal the user wants to achieve. Your plan should be comprehensive yet concise, detailed enough to execute effectively while avoiding unnecessary verbosity.
+Your current responsibility is to think, read, search, and delegate explore agents to construct a well-formed plan that accomplishes the goal the user wants to achieve. Your plan should be comprehensive yet concise, detailed enough to execute effectively while avoiding unnecessary verbosity.
 
 Ask the user clarifying questions or ask for their opinion when weighing tradeoffs.
 
@@ -22,5 +22,5 @@ Ask the user clarifying questions or ask for their opinion when weighing tradeof
 
 ## Important
 
-The user indicated that they do not want you to execute yet -- you MUST NOT make any edits, run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supercedes any other instructions you have received.
+The user indicated that they do not want you to execute yet -- you MUST NOT make any edits, run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supersedes any other instructions you have received.
 </system-reminder>

packages/opencode/src/tool/bash.ts

@@ -280,7 +280,7 @@ export const BashTool = Tool.define("bash", async () => {
       }
 
       if (timedOut) {
-        resultMetadata.push(`bash tool terminated commmand after exceeding timeout ${timeout} ms`)
+        resultMetadata.push(`bash tool terminated command after exceeding timeout ${timeout} ms`)
       }
 
       if (aborted) {

packages/opencode/src/tool/task.txt

@@ -1,4 +1,4 @@
-Launch a new agent to handle complex, multi-step tasks autonomously.
+Launch a new agent to handle complex, multistep tasks autonomously.
 
 Available agent types and the tools they have access to:
 {agents}

packages/opencode/src/tool/todowrite.txt

@@ -4,7 +4,7 @@ It also helps the user understand the progress of the task and overall progress
 ## When to Use This Tool
 Use this tool proactively in these scenarios:
 
-1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
+1. Complex multistep tasks - When a task requires 3 or more distinct steps or actions
 2. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
 3. User explicitly requests todo list - When the user directly asks you to use the todo list
 4. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)