After reviewing this, I see that the search returns route IDs rather than page IDs, which could result in the wrong pages being edited (or deleted!) if more specific criteria are used. Because this can lead to unintentional deletion of content, this will fall under the umbrella of a coming Patch Level release. There is no reason to make this issue private, because it is not possible to exploit this issue.
In your case, even though you wanted to apply the change to all wiki pages, this had an effect because although all page IDs should have route IDs, not all route IDs refer to page IDs. For example, even if Page A has Page-ID 2 and Route-ID 20, it was possible that Page-ID 20 did not exist. Conversely, if Route-ID 3 referred to a synonym, then Page-ID 3 would not have been affected by the edit. Anyway, this is resolved on your site, so you should be able to continue making edits.
This issue is a leftover from 2015, when the search system was updated to use route data, but the design of the vBulletin 3 search did not require this change. This has resulted in incorrect search results under vBulletin 3 since that time. The massive search was designed to use our custom vBulletin 3 search engine, because it allows both more specific and less specific criteria than the search engines in either vBulletin 4 or XenForo allow. By fixing this issue, VaultWiki on vBulletin 3 will now have correct search results.