Unsaved tabs and saved files are not the same replacement target. The verified path covered previewing replacements in saved files; it did not confirm replacing unsaved tab contents while preserving their unsaved state. Do not broaden the result. Decide what each tab should become before running a workspace replacement.
Inventory tabs separately from files
List eight saved chapters, two unsaved tabs, fourteen old spellings, and four excluded reference matches. Mark every item as included, excluded, or awaiting a save decision. An unsaved scratch tab may deserve exclusion; an unsaved chapter edit may need a separately named working file.
Saving is not a clerical detail. It determines which bytes can be previewed, reversed, and recovered after replacement.
Make the target set safe before preview
For tabs whose content should survive, save a working copy under a clear name. Leave experimental tabs out of the bulk operation and edit them individually if needed. This turns the workspace replacement into a set of recoverable files.
In Rune Studio, preview the old term across that saved scope. Compare file, line, and context with the expected fourteen included occurrences and four excluded ones. A preview from saved files must not be assumed to include unsaved memory state.
Apply only the confirmed saved scope
After context review, apply to the saved working copies, count the new spelling, and reverse-search the old one. Documented exclusions may remain. Reopen representative files before accepting the result.
The unverified unsaved-tab path should remain unverified in the conclusion. Convenience does not justify pretending that state preservation was tested.
Use a per-tab reconciliation list
When the safe fallback is to handle saved copies one at a time, list each file, its expected old-term count, its new-term count, and whether it has been reopened. For two matches per file, finish only after the old term is at zero and the new term is at two in every copy. Check Rune Studio’s tab labels for any remaining unsaved indicator before closing. If a temporary note cannot be saved in place, export its text to a clearly named file and keep the original tab untouched until the copy has been verified.
Preserve decisions before automation
The safe goal is not “include everything.” It is “replace only items whose persistence and rollback are understood.” Rune Studio supports previewed search and replacement for saved workspace files; check the current scope on the Rune Studio product page. Begin by dividing open tabs into save, exclude, and decide-later groups.