Nine search matches do not mean nine edits. The planned 3,000-character chapter requires seven narrative uses to be separated from two quotation or dialogue exceptions by reading their context. Hands-on verification confirmed a single-file match count, one replacement, and reverse searches for the old and new terms. It did not exercise Cmd+F, selection-to-query transfer, result navigation, or the nine-item classification.
Separate the observed single-file search from the nine-item classification
A find-in-file pass is complete when every occurrence has a role. In one chapter with nine matches, classify seven narrative uses as revision candidates and two dialogue or quotation uses as intentional exceptions. Search gathers evidence without changing the manuscript.
Record the query, chapter, and starting count. Selected text may seed the query, but context still determines meaning.
Read surrounding sentences and speaker
Check the sentence before and after, the speaker, quotation source, and section role. Narrative text may follow a style rule while character speech deliberately does not. The token alone cannot decide.
Do not identify an occurrence only as match three. Add a heading or nearby phrase so it can be found after later edits change the count.
Keep the first pass read-only
Replacing during search makes recovery difficult when a later exception changes the rule. Classify all nine first. Hand the seven approved edits to the single-chapter exception-aware replacement workflow only after the rule is stable.
Do not change the query when another variant appears. Record a new candidate and finish the current pass.
Explain count differences
Eight instead of nine calls for checking case, width, line boundaries, and selection scope. Ten calls for classifying the additional occurrence. A count difference is evidence to investigate, not proof of corruption.
This article remains in one file. Workspace totals belong to the cross-file match-and-file count workflow and multi-file replacement to the bounded multi-file replacement workflow.
Keep only the observed single-file search and replace scope
Current macOS Rune Studio documentation states that Command-F opens the standard find bar, selected text can seed a query, matches can be navigated, and replacement controls can follow.
The August 14, 2026 hands-on verification common sample confirmed a single-file match count, a literal replacement, and reverse searches for old and new forms. It did not observe the Command-F screen, selected-text seeding, next/previous navigation, wrap detection, or the article’s nine-match classification. The seven-versus-two decision remains human editorial work.
Treat the nine-row procedure as an unrun test plan rather than an article-specific product pass. Review documented scope on the Rune Studio product page. Workspace replacement, regular-expression reference material, semantic automation, and replacement execution are excluded from this article.
Read the nine matches by meaning
In a general find-in-file review, copy one sentence before and after each of the nine occurrences. For the seven narrative matches, ask whether nearby repetition is accidental or deliberate point-of-view emphasis. Put the dialogue match in a voice exception and the quotation in protected source text. This nine-match navigation was not observed in the current Rune Studio hands-on verification run.
Do not propose alternatives during the first pass because that changes the query and the reader’s criterion. Record only candidate or intentional exception plus the reason.
Explain a count of eight or ten before editing
If the same file yields eight matches, check character width, inflection, scope, and unsaved state. If it yields ten, check whether a heading or note has entered the scope. Once nine is restored, save a short opening fragment beside each line number so later edits do not make the evidence impossible to find. Verify seven narrative, one dialogue, and one quotation, then close the search without replacement.
Do not convert the search list into a replacement rule
Even after dialogue and quotation are excluded, the semantic condition “narrative only” may not be expressible as a safe replacement rule. Hand the seven candidates to a context-reading edit. If the bounded multi-file replacement workflow or the single-chapter exception-aware replacement workflow follows, build a new scope and preview; the nine-match list is evidence, not an execution command.
Separate search order from narrative importance
Search-result order does not express narrative importance. Number results in that order but attach a stable scene heading. Even after seven consecutive revision candidates, continue to the final quotation exception before freezing the rule.
In a long chapter, the search can wrap to the first result without an obvious boundary. Record a short phrase around the starting occurrence; returning to it marks one complete pass and prevents duplicate classification.
Write the replacement rule from the evidence
Summarize the seven candidates with one rule, for example: standardize this spelling in narration while preserving dialogue and quoted source text. If that rule cannot be written, the search findings are not ready for handoff.
Include scope, exceptions, and authority. The deliverable of this article is the nine-row classification and the rule—not an edited manuscript.
Reorder the nine matches for editorial handoff
Do not hand matches over as a raw navigation order. Group the seven narrative candidates together, then keep the dialogue and protected quotation as named exceptions. Include a short opening fragment with each line number so the sentence remains traceable after later edits.
The local-search task ends when all nine have classifications and reasons. It does not end by forcing the result count to zero.
Conditions for closing the nine-match search list
-
Freeze query, chapter, and nine-match baseline
-
Attach surrounding sentences, speaker, quotation source, and scene heading
-
Classify seven narrative candidates and two intentional exceptions
-
Keep the first pass read-only
-
Do not change query when another variant appears
-
Record the starting phrase to detect search wraparound
-
Investigate eight or ten results instead of forcing nine
-
Separate search order from narrative importance
-
Use the project style rule rather than majority form
-
Write one rule covering seven targets and two exceptions
-
Do not add results from other files
-
Deliver the nine-row classification and rule, not edited text
Hand the search evidence to the next editor
Prepare a one-file test card for the repeated phrase and classify all nine matches: seven narrative candidates, one dialogue exception, and one protected quotation. Attach surrounding sentences and reasons, then hand the seven candidates to the editor without replacing a character or counting other files. Review the documented local-search scope on the Rune Studio product page without treating the unrun Command-F and nine-match route as observed evidence.