Fix Kiro IDE tests - move to unit tests with proper setup

- Remove problematic feature test that used Laravel helpers
- Add Kiro detection tests to existing unit test suite
- Follow established testing patterns with temporary directories
- Ensure tests don't depend on Laravel application context

Author: mr-wolf-gb

tests/Feature/Install/CodeEnvironmentsDetectorTest.php

@@ -236,3 +236,24 @@
     unlink($tempDir.'/CLAUDE.md');
     rmdir($tempDir);
 });
+
+test('discoverProjectInstalledCodeEnvironments detects kiro with kiro directory', function () {
+    $tempDir = sys_get_temp_dir().'/boost_test_'.uniqid();
+    mkdir($tempDir);
+    mkdir($tempDir.'/.kiro');
+
+    $detected = $this->detector->discoverProjectInstalledCodeEnvironments($tempDir);
+
+    expect($detected)->toContain('kiro');
+
+    // Cleanup
+    rmdir($tempDir.'/.kiro');
+    rmdir($tempDir);
+});
+
+test('getCodeEnvironments includes kiro', function () {
+    $environments = $this->detector->getCodeEnvironments();
+
+    expect($environments)->toHaveKey('kiro');
+    expect($environments->get('kiro'))->toBeInstanceOf(\Laravel\Boost\Install\CodeEnvironment\Kiro::class);
+});