fix: use Unicode-aware regex for identifier matching and fix misleading test claims

- Replace [$\w]+ with [\p{ID_Continue}$]+ (with u flag) in extractSpecifierComments
  to correctly match Unicode identifiers (α, β, Ω, café, etc.) not just ASCII
- Add B6c test verifying Unicode specifiers with trailing comments are preserved
- Fix INDENT-L1 test name: old extension reads editor.tabSize, not hardcoded 4
- Fix broken reference to non-existent 999-manual-proof.test.ts
- Fix type-only-imports-comparison.test.ts: clarify it only tests new extension
- Fix re-export test comments: old extension doesn't touch re-exports at all

Author: JohannesHoppe

src/imports/import-manager.ts

@@ -367,7 +367,8 @@ export class ImportManager {
         const rest = leadingBlockMatch[2];
 
         // Extract specifier name from rest (might be "A," or "A as B," etc.)
-        const specMatch = rest.match(/^(?:type\s+)?([$\w]+)/);
+        // Use \p{ID_Continue} to match all valid ECMAScript identifier characters (including Unicode)
+        const specMatch = rest.match(/^(?:type\s+)?([\p{ID_Continue}$]+)/u);
         if (specMatch) {
           const specName = specMatch[1];
           if (specifierNames.includes(specName)) {
@@ -380,7 +381,8 @@ export class ImportManager {
       }
 
       // Check for trailing line comment: specifier // comment
-      const trailingLineMatch = trimmed.match(/^(?:type\s+)?([$\w]+)(?:\s+as\s+[$\w]+)?\s*,?\s*(\/\/.*?)$/);
+      // Use \p{ID_Continue} to match all valid ECMAScript identifier characters (including Unicode)
+      const trailingLineMatch = trimmed.match(/^(?:type\s+)?([\p{ID_Continue}$]+)(?:\s+as\s+[\p{ID_Continue}$]+)?\s*,?\s*(\/\/.*?)$/u);
       if (trailingLineMatch) {
         const specName = trailingLineMatch[1];
         const comment = trailingLineMatch[2];
@@ -394,7 +396,8 @@ export class ImportManager {
       }
 
       // Regular specifier without comments
-      const regularMatch = trimmed.match(/^(?:type\s+)?([$\w]+)/);
+      // Use \p{ID_Continue} to match all valid ECMAScript identifier characters (including Unicode)
+      const regularMatch = trimmed.match(/^(?:type\s+)?([\p{ID_Continue}$]+)/u);
       if (regularMatch) {
         const specName = regularMatch[1];
         if (specifierNames.includes(specName) && !result.has(specName)) {

tests/comparison/test-cases/type-only-imports-comparison.test.ts

@@ -1,19 +1,24 @@
 /**
- * Type-Only Import Handling - Legacy vs Modern Mode Comparison
+ * Type-Only Import Handling - Legacy vs Modern Mode (NEW EXTENSION ONLY)
+ *
+ * NOTE: Despite being in the comparison test directory, this file does NOT run the
+ * old TypeScript Hero extension. It only tests the new extension's behavior in both
+ * legacy and modern modes. The old extension cannot be tested here because its
+ * typescript-parser predates TypeScript 3.8 and cannot parse `import type` syntax.
+ *
+ * For VERIFIED old extension behavior with `import type`, see:
+ * - tests/comparison/test-cases/06-edge-cases.test.ts (test 086)
+ * - tests/comparison/test-cases/11-true-compatibility.test.ts (TC7a, TC7b)
  *
  * This test demonstrates the key difference in type-only import handling between:
  * - Legacy mode (legacyMode: true): Strips `import type` keywords, allows merging with value imports
  * - Modern mode (legacyMode: false): Preserves `import type` keywords, keeps type/value imports separate
- *
- * **Why the difference?**
- * - Old extension: Pre-TypeScript 3.8, before `import type` was introduced
- * - Modern mode: Respects TypeScript 3.8+ semantics for type-only imports
  */
 
 import * as assert from 'assert';
 import { organizeImportsNew } from '../new-extension/adapter';
 
-suite('Type-Only Import Handling: Legacy vs Modern', () => {
+suite('Type-Only Import Handling: Legacy vs Modern (new extension only)', () => {
 
   test('LEGACY MODE: Strips import type keywords', async () => {
     // SCENARIO: import type statement

tests/unit/import-manager.edge-cases-audit.test.ts

@@ -223,7 +223,7 @@ const x = A + B + Z;
 `;
 
     // LEGACY MODE: Strip comments to match old TypeScript Hero extension
-    // (Proven in tests/comparison/test-cases/999-manual-proof.test.ts)
+    // (Verified in tests/comparison/test-cases/00-shared-behavior.test.ts and 11-indentation-behavior.test.ts L4)
     const expected = `import { A, B, Z } from 'lib';
 
 const x = A + B + Z;
@@ -354,6 +354,46 @@ const x = A + a + B + b + Ä + ä + α + β + Ω;
     }
   });
 
+  // ============================================================================
+  // B6c: Unicode specifiers WITH comments (regression test for \p{ID_Continue} regex)
+  // ============================================================================
+
+  test('B6c: Unicode specifiers with trailing comments are preserved', async () => {
+    // This tests that the extractSpecifierComments regex handles Unicode identifier
+    // characters (not just ASCII [$\w]). ECMAScript allows Unicode letters in identifiers.
+    const content = `import {
+  Ω, // Greek capital letter omega
+  α, // Greek small letter alpha
+  café, // French word with accent
+} from 'lib';
+
+const x = Ω + α + café;
+`;
+
+    // Sorted alphabetically (case-insensitive), comments must travel with their specifiers
+    const expected = `import {
+  café, // French word with accent
+  α, // Greek small letter alpha
+  Ω, // Greek capital letter omega
+} from 'lib';
+
+const x = Ω + α + café;
+`;
+
+    const doc = await createTempDocument(content, 'ts');
+    try {
+      const config = new ImportsConfig();
+      const manager = new ImportManager(doc, config);
+      const edits = await manager.organizeImports();
+      await applyEditsToDocument(doc, edits);
+
+      const result = doc.getText();
+      assert.strictEqual(result, expected, 'Unicode specifier comments must be preserved when sorting');
+    } finally {
+      await deleteTempDocument(doc);
+    }
+  });
+
   // ============================================================================
   // B7: Path case sensitivity
   // ============================================================================
@@ -804,7 +844,7 @@ import { Y } from './m';
 const foo = Y;
 `;
 
-    // Expected: Re-exports are moved AFTER imports (matching old TypeScript Hero behavior)
+    // Expected: Re-exports are placed AFTER organized imports (old extension doesn't touch re-exports at all)
     const expected = `import { Y } from './m';
 
 export { X } from './m';

tests/unit/import-manager.edge-cases.test.ts

@@ -783,7 +783,7 @@ import { Y } from './m';
 const foo = Y;
 `;
 
-    // Expected: Re-exports are moved AFTER imports (matching old TypeScript Hero behavior)
+    // Expected: Re-exports are placed AFTER organized imports (old extension doesn't touch re-exports at all)
     const expected = `import { Y } from './m';
 
 export { X } from './m';

tests/unit/import-manager.indentation.test.ts

@@ -7,14 +7,14 @@ import { createTempDocument, deleteTempDocument } from './test-helpers';
  * ImportManager - Indentation Tests
  *
  * These tests verify that our indentation implementation:
- * 1. Legacy mode: Matches old TypeScript Hero (always spaces, 4-space default)
+ * 1. Legacy mode: Matches old TypeScript Hero (always spaces, reads from editor.tabSize)
  * 2. Modern mode: Enhanced UX (supports tabs, 2-space default)
  * 3. useOnlyExtensionSettings: Provides full control
  */
 
 suite('ImportManager - Indentation - Legacy Mode', () => {
 
-  test('INDENT-L1: Default 4 spaces in legacy mode', async () => {
+  test('INDENT-L1: Uses editor.tabSize in legacy mode (VS Code default is 4)', async () => {
     const content = `import { VeryLongComponentName, AnotherLongName, ThirdName, FourthName, FifthName } from 'library';
 
 const x = VeryLongComponentName;
@@ -56,7 +56,7 @@ const b = FifthName;
       await (await import('vscode')).workspace.applyEdit(edit);
 
       const result = doc.getText();
-      assert.strictEqual(result, expected, 'Legacy mode must use 4-space indentation by default');
+      assert.strictEqual(result, expected, 'Legacy mode uses editor.tabSize for indentation (VS Code general default is 4)');
     } finally {
       await deleteTempDocument(doc);
     }