⚡ Bolt: Replace Regex with manual string parsing in HintExtractor

[himattm]

💡 What: The optimization implements a manual single-pass string parser using a StringBuilder in HintExtractor.kt, eliminating five separate Regex variables that parsed strings via .replace() and .matches().

🎯 Why: The original implementation allocated numerous intermediate strings as it mutated strings with sequential Regex.replace and Regex.matches operations. In Kotlin Multiplatform (e.g. JVM/WasmJs), replacing regex parsing pipelines with native string loops and indexing is highly optimized, removing compilation, state-machine tracking overheads, and backtracking limits.

📊 Impact: Heavily improves execution performance by compiling the pipeline into a simple array loop, greatly reducing GC pressure via reduced string allocations, especially helpful given this file processes user strings in a hot path.

🔬 Measurement: To verify the improvement, run the unit test module using ./gradlew :halogen-engine:test focusing on the module's HintExtractorTest.kt.

---

PR created automatically by Jules for task 9791098139604862893 started by @himattm

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[himattm]

Closing this in favor of #74, which curates the parser hot-path changes without the generated .jules/bolt.md metadata and covers the duplicate HintExtractor/SchemaParser optimization work in one PR.

[google-labs-jules]

Closing this in favor of #74, which curates the parser hot-path changes without the generated .jules/bolt.md metadata and covers the duplicate HintExtractor/SchemaParser optimization work in one PR.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.