Replace text across files

Replace the deprecated API name fetchRecordsV1 with fetchRecords in all JavaScript and TypeScript files, run the test suite, and produce a short list of files that required manual fixes after automated replacement.

Before mass-replacing fetchRecordsV1 with fetchRecords, show me occurrences that look like public API surfaces — exported functions, client SDKs, and README examples — and flag places where a naive replace would break backward compatibility or external tutorials.

I ran a project-wide replace of fetchRecordsV1 to fetchRecords and now the SDK and some examples fail to compile. I didn’t know which files were part of the public API. I’m worried we’ve broken external consumers. What likely mistakes did I make and what are the fastest steps to identify and revert the problematic changes selectively?

I routinely do bulk text replacements and twice this quarter we shipped changes that broke external SDKs or docs. I need a repeatable habit to avoid that without manual per-file checks. Which change to my replace workflow — testing, naming rules, or preflight scripts — will save the most time and prevent consumer breakage?