Refactor test enforcement logic in InstallCommand

Simplifies the determineTestEnforcement method by removing the minimum test file check and always prompting the user to decide if AI should create tests. Updates collectInstallationPreferences to match the new method signature.

Author: sagalbot

src/Console/InstallCommand.php

@@ -118,9 +118,9 @@ private function discoverEnvironment(): void
     private function collectInstallationPreferences(): void
     {
         $this->selectedBoostFeatures = $this->selectBoostFeatures();
-        $this->enforceTests = $this->determineTestEnforcement(ask: false);
         $this->selectedTargetMcpClient = $this->selectTargetMcpClients();
         $this->selectedTargetAgents = $this->selectTargetAgents();
+        $this->enforceTests = $this->determineTestEnforcement();
     }
 
     private function performInstallation(): void
@@ -196,23 +196,13 @@ private function hyperlink(string $label, string $url): string
      * won't have the CI setup to make use of them anyway, so we're just wasting their
      * tokens/money by enforcing them.
      */
-    protected function determineTestEnforcement(bool $ask = true): bool
+    protected function determineTestEnforcement(): bool
     {
-        $hasMinimumTests = Finder::create()
-            ->in(base_path('tests'))
-            ->files()
-            ->name('*.php')
-            ->count() > 6;
-
-        if (! $hasMinimumTests && $ask) {
-            $hasMinimumTests = select(
-                label: 'Should AI always create tests?',
-                options: ['Yes', 'No'],
-                default: 'Yes'
-            ) === 'Yes';
-        }
-
-        return $hasMinimumTests;
+        return select(
+            label: 'Should AI always create tests?',
+            options: ['Yes', 'No'],
+            default: 'Yes'
+        ) === 'Yes';
     }
 
     /**