Workspace search begins with scope, not with the query. Decide whether the result covers chapters, references, saved notes, and actual unsaved tabs before interpreting a count.
The actual sample contained 12 saved Markdown chapters, a saved file under refs, and one saved stand-in named notes/unsaved-standin.md. Chapter-only search returned 18 matches across 12 files, refs returned four, and the search across 14 saved Markdown files returned 23. The arithmetic is 18 + 4 + 1 saved stand-in match. No real unsaved tab was created or searched, and unsaved_tab_included=false, so status remains partial. Search changed no files.
Record root, extension, exclusions, and save state
A product-independent search card names the root, included folder, extension, exclusions, and treatment of saved versus unsaved content. Here the question is limited to 12 chapter Markdown files, so the four refs matches and the saved stand-in match do not contribute to the chapter acceptance count. A saved stand-in is not evidence of actual unsaved-tab behavior.
Keep match count and matched-file count separate. Eighteen matches across twelve files means at least some files contain more than one match.
Expand from narrow scope to the whole workspace
Search only the chapter folder and Markdown extension first, recording 18 matches in 12 files. Search refs separately and record four candidates. Only then search the entire workspace and record 23.
Eighteen plus four plus the match in notes/unsaved-standin.md is 23. The final match is therefore known and saved; it is neither unresolved nor attributable to an unsaved tab. Classifying the result paths as chapters, refs, and notes explains the full saved-workspace count.
What Stage 4 established
The five operations returned chapter_files=12, chapter_matches=18, chapter_match_files=12, excluded_ref_matches=4, workspace_matches=23, and unsaved_tab_included=false.
These are counts from 14 saved Markdown files. The 23 matches divide into 18 chapter matches, four refs matches, and one saved stand-in match. Match meaning, visual highlighting, and actual unsaved-tab inclusion were not verified. The known saved count must not be promoted into an unsaved-tab success claim.
Keep search separate from replacement
Rune Studio’s public documentation describes workspace-wide search. That Stage 3 feature is separate from the Stage 4 counts. No edit or replacement occurred.
STUDIO-570 previews 17 old-form matches and applies 14 approved replacements. This article stops at defining and explaining the search set. It does not claim reverse-search or unsaved-tab behavior.
Close the saved scope without claiming unsaved-tab coverage
The chapter set of 18/12, four refs matches, and one saved stand-in match explain all 23 saved-workspace matches. If scope changes, rerun the chapter, refs, stand-in, and workspace counts. Testing a real unsaved tab requires a separate run rather than relabeling the saved stand-in.
Clear the query when finished; file changes remain zero. The output is an auditable scope record, not an edited manuscript. The Rune Studio product page describes the available workspace-search feature.
