fix: regular expressions in ripgrep

[uinstinct]

Description

Previously, none of the searches involving regex characters like * or | always produced empty results. Escaping the regex during prepareQueryForRipgrep added escaping characters \ which were passed down to ripgrep. Ripgrep guide suggests the regular expression does not need escaping. If we need to search for exact string, -F flag needs to used.

resolves CON-4741

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-review

Checklist

• [] I've read the contributing guide
• [] The relevant docs, if any, have been updated or created
• [] The relevant tests, if any, have been updated or created

Screen recording or screenshot

before	after

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

---

Summary by cubic

Fixes ripgrep searches by treating queries as regex patterns and removing accidental escaping, so operators like |, * and character classes now work. Addresses CON-4741.

• Bug Fixes
  • Removed literal-escaping in prepareQueryForRipgrep; pass queries to ripgrep as-is.
  • Updated GrepSearch tool text to clearly expect a regex pattern.

^{Written for commit b784015. Summary will update automatically on new commits.}

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="core/tools/definitions/grepSearch.ts">

<violation number="1" location="core/tools/definitions/grepSearch.ts:24">
The alternation example in the query description is missing the closing quote, so the illustrated pattern isn’t valid and can confuse users copying it.</violation>
</file>

_{Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR}