Plan complex repairs before editing

src/lai_automation/agent.py

@@ -91,4 +91,12 @@ class AiderAgent:
         for filename in files:
             if (task_file.parent.parent / filename).is_file():
                 command.extend(["--file", filename])
+        if files:
+            command.extend([
+                "--architect",
+                "--editor-model",
+                self.settings.agent_model,
+                "--editor-edit-format",
+                "udiff",
+            ])
         return command

src/lai_automation/prompt.py

@@ -118,6 +118,10 @@ When expected behavior names tables from multiple databases or connections, firs
 routing and existing staged-query workflows. Do not put an impossible cross-connection join only
 in ERP semantics. Implement deterministic orchestration that resolves identifiers in one source
 and passes only the required identifier into the next source, preserving tenant isolation.
+For this cross-database report, editing only config/*_semantics.php or tests is an invalid repair.
+You MUST implement production behavior in ChatController or TenantDatabaseService and cover that
+exact application method in ChatControllerSourceResolutionTest. Before editing, describe the data
+flow, connection used at each stage, and where the final result is assembled.
 """
     placeholder_guidance = ''
     if '__LAI_' in response: