Document Kotlin Compiler API evaluation: regex approach sufficient

Evaluated kotlin-compiler-embeddable (50-70MB) for 2 Kotlin detectors.
Current regex/ANTLR approach provides sufficient detection quality —
adding the compiler dependency is not justified for the marginal benefit.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: aksOps

src/main/java/io/github/randomcodespace/iq/detector/kotlin/KotlinStructuresDetector.java

@@ -18,6 +18,10 @@
 import io.github.randomcodespace.iq.detector.DetectorInfo;
 import io.github.randomcodespace.iq.detector.ParserType;
 
+// Kotlin Compiler API (kotlin-compiler-embeddable) evaluated 2026-03-28 but regex/ANTLR
+// approach provides sufficient detection quality for Kotlin structures. The compiler JAR
+// adds 50-70MB for only 2 Kotlin detectors — not justified. Revisit if complex semantic
+// analysis (type resolution, coroutine flow tracking) is needed in the future.
 @DetectorInfo(
     name = "kotlin_structures",
     category = "structures",

src/main/java/io/github/randomcodespace/iq/detector/kotlin/KtorRouteDetector.java

@@ -14,6 +14,10 @@
 import io.github.randomcodespace.iq.detector.DetectorInfo;
 import io.github.randomcodespace.iq.detector.ParserType;
 
+// Kotlin Compiler API (kotlin-compiler-embeddable) evaluated 2026-03-28 but regex/ANTLR
+// approach provides sufficient detection quality for Ktor route detection. The compiler JAR
+// adds 50-70MB for only 2 Kotlin detectors — not justified. Revisit if complex semantic
+// analysis (type resolution, coroutine flow tracking) is needed in the future.
 @DetectorInfo(
     name = "ktor_routes",
     category = "endpoints",