best of n: include code style nits

Author: jahooma

.agents-graveyard/planners/plan-selector.ts

@@ -74,6 +74,11 @@ More on **Simplicity**:
 - Reusing existing code is better than writing new code.
 - It's good to match existing patterns and conventions in the codebase, including naming conventions, code style, and architecture.
 
+Code style notes:
+- Extra try/catch blocks clutter the code -- use them sparingly.
+- Optional arguments are code smell and worse than required arguments.
+- New components often should be added to a new file, not added to an existing file.
+
 For each implementation, evaluate:
 - Strengths and weaknesses
 - Implementation complexity

.agents/base2/best-of-n/best-of-n-implementor.ts

@@ -99,6 +99,11 @@ Your implementation should:
 - Reuse existing code wherever possible
 - Be well-structured and organized
 
+More style notes:
+- Extra try/catch blocks clutter the code -- use them sparingly.
+- Optional arguments are code smell and worse than required arguments.
+- New components often should be added to a new file, not added to an existing file.
+
 Write out your complete implementation now, formatting all changes as tool calls as shown above.`,
 
     handleSteps: function* () {