Tweak todo's prompt to not be used for trivial tasks

Author: jahooma

.agents/base2/base2.ts

@@ -193,7 +193,7 @@ The user asks you to implement a new feature. You respond in multiple steps:
 ${buildArray(
   `- Spawn file pickers, code-searcher, directory-lister, glob-matcher, commanders, and web/docs researchers to gather context as needed. The file-picker-max agent in particular is very useful to use to find relevant files. Read all the relevant files using the read_files tool. Read as many files as possible so that you have a comprehensive context on the user's request.`,
   `- Important: Read as many files as could possibly be relevant to the task to improve your understanding of the user's request and produce the best possible code changes. This is frequently 12-20 files, depending on the task.`,
-  `- Use the write_todos tool to write out your step-by-step implementation plan. Include ALL of the applicable tasks in the list.${hasNoValidation ? '' : ' You should include at least one step to validate/test your changes: be specific about whether to typecheck, run tests, run lints, etc.'}`,
+  `- For multi-step tasks, use the write_todos tool to write out your step-by-step implementation plan. Include ALL of the applicable tasks in the list.${hasNoValidation ? '' : ' You should include at least one step to validate/test your changes: be specific about whether to typecheck, run tests, run lints, etc.'} Skip write_todos for trivial tasks like single-line edits or simple questions.`,
   `- You must spawn the ${isGpt5 ? 'best-of-n-editor-gpt-5' : 'best-of-n-editor'} agent to implement non-trivial code changes, since it will generate the best code changes from multiple implementation proposals. This is the best way to make high quality code changes -- strongly prefer using this agent over the str_replace or write_file tools, unless the change is very small and trivial.`,
   !hasNoValidation &&
     `- Test your changes${isFast ? ' briefly' : ''} by running appropriate validation commands for the project (e.g. typechecks, tests, lints, etc.).${isFast ? ' If you can, only typecheck/test the area of the project that you are editing, rather than the entire project.' : ' Start by type checking the specific area of the project that you are editing and then test the entire project if necessary.'} You may have to explore the project to find the appropriate commands. Don't skip this step!`,

common/src/tools/params/tool/write-todos.ts

@@ -21,7 +21,7 @@ export const writeTodosParams = {
         ),
     })
     .describe(
-      'Write a todo list to track tasks. Use this frequently to maintain a step-by-step plan.',
+      'Write a todo list to track tasks for multi-step implementations. Use this frequently to maintain an updated step-by-step plan.',
     ),
   outputs: z.tuple([
     z.object({