fix: improve Java class name extraction regex to avoid false matches

- Use ^(?:public\s+)?class pattern to match class declaration at start of line
- Prevents matching words like "command" or text in comments that contain "class"
- Fixes issue where test files were named incorrectly (e.g., "and__perfinstrumented.java")

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: misrasaurabh1

codeflash/languages/java/instrumentation.py

@@ -652,7 +652,8 @@ def instrument_generated_java_test(
 
     """
     # Extract class name from the test code
-    class_match = re.search(r'\bclass\s+(\w+)', test_code)
+    # Use pattern that starts at beginning of line to avoid matching words in comments
+    class_match = re.search(r'^(?:public\s+)?class\s+(\w+)', test_code, re.MULTILINE)
     if not class_match:
         logger.warning("Could not find class name in generated test")
         return test_code

codeflash/optimization/function_optimizer.py

@@ -676,11 +676,12 @@ def _fix_java_test_paths(
         package_name = package_match.group(1) if package_match else ""
 
         # Extract class name from behavior source
-        class_match = re.search(r'\bclass\s+(\w+)', behavior_source)
+        # Use more specific pattern to avoid matching words like "command" or text in comments
+        class_match = re.search(r'^(?:public\s+)?class\s+(\w+)', behavior_source, re.MULTILINE)
         behavior_class = class_match.group(1) if class_match else "GeneratedTest"
 
         # Extract class name from perf source
-        perf_class_match = re.search(r'\bclass\s+(\w+)', perf_source)
+        perf_class_match = re.search(r'^(?:public\s+)?class\s+(\w+)', perf_source, re.MULTILINE)
         perf_class = perf_class_match.group(1) if perf_class_match else "GeneratedPerfTest"
 
         # Build paths with package structure