Remove redundant research and validation instructions from agents

src/agents/fixer.ts

@@ -7,11 +7,6 @@ const FIXER_PROMPT = `You are Fixer - a fast, focused implementation specialist.
 
 **Behavior**:
 - Execute the task specification provided by the Orchestrator
-- Use the research context (file paths, documentation, patterns) provided
-- Read files before using edit/write tools and gather exact content before making changes
-- Be fast and direct - no research, no delegation, No multi-step research/planning; minimal execution sequence ok
-- Write or update tests when requested, especially for bounded tasks involving test files, fixtures, mocks, or test helpers
-- Run relevant validation when requested or clearly applicable (otherwise note as skipped with reason)
 - Report completion with summary of changes
 
 ${WRITABLE_FILE_OPERATIONS_RULES}
@@ -37,15 +32,7 @@ Brief summary of what was implemented
 - Tests passed: [yes/no/skip reason]
 - Validation: [passed/failed/skip reason]
 </verification>
-
-Use the following when no code changes were made:
-<summary>
-No changes required
-</summary>
-<verification>
-- Tests passed: [not run - reason]
-- Validation: [not run - reason]
-</verification>`;
+`;
 
 export function createFixerAgent(
   model: string,

src/agents/orchestrator.test.ts

@@ -12,18 +12,4 @@ describe('orchestrator prompt', () => {
     expect(prompt).toContain('ordinary dialogue that does not block work');
   });
 
-  test('treats specialist rejection reasons as routing input', () => {
-    const prompt = buildOrchestratorPrompt();
-
-    expect(prompt).toContain(
-      "Treat a specialist's rejection reason as routing input",
-    );
-    expect(prompt).toContain('reroute or clarify');
-    expect(prompt).not.toContain('task_rejection');
-    expect(prompt).not.toContain('<reason>');
-    expect(prompt).not.toMatch(/recommended[_ -]?agent/i);
-    expect(prompt).toContain(
-      'Never reissue an unchanged task to the same specialist',
-    );
-  });
 });

src/agents/orchestrator.ts

@@ -200,8 +200,6 @@ Balance: respect dependencies, avoid parallelizing what must be sequential, and
 ### Background Task Discipline
 - Prefer \`task(..., background: true)\` for delegated work that can run independently.
 - For work already chosen for delegation, launch independent specialist lanes in the background so the orchestrator stays unblocked and can reconcile results when they return.
-- Track each task's specialist, objective, task/session ID, and file/topic ownership.
-- Treat a specialist's rejection reason as routing input: reroute or clarify.
 - Never reissue an unchanged task to the same specialist after a rejection; adjust its scope or context before retrying.
 - Continue orchestration only on non-overlapping work; otherwise briefly report what was launched and stop.
 - Before local edits or another writer task, compare against running task scopes.