test(views): source-level naming regression locking out "saved query"

I added a test that reads pearl.el and asserts the user-facing "saved query" phrase appears nowhere, so the rename can't silently regress. Internal helpers keep the hyphenated saved-query symbol fragment, which a user never sees. The banned thing is the two-word user-facing phrase in any prompt, message, transient label, or docstring.

This is the cross-cutting net over Phase 8. The per-phase tests already cover the account guard, cross-store dedup and dispatch, reverse-compile round-trips and refusals, and the metadata-preserving writer. The live create, edit, run, publish, save-locally, refuse, and delete end-to-end needs a real Linear workspace and is filed as a manual-verify checklist.

Suite at 777 green, compile and lint clean.

1 files changed, 10 insertions, 0 deletions

diff --git a/tests/test-pearl-naming.el b/tests/test-pearl-naming.el
index 383b913..cf3bd13 100644
--- a/tests/test-pearl-naming.el
+++ b/tests/test-pearl-naming.el
@@ -73,5 +73,15 @@
                    "")))
       (should-not (string-match-p "saved quer" doc)))))
 
+(ert-deftest test-pearl-naming-no-user-facing-saved-query-phrase ()
+  "The Pearl-invented \"saved query\" phrase appears nowhere in pearl.el.
+Internal helpers may keep the hyphenated `saved-query' symbol fragment, but no
+user-facing prompt, message, transient label, or docstring says \"saved query\".
+This is the source-level naming regression that locks the rename."
+  (let ((src (with-temp-buffer
+               (insert-file-contents (find-library-name "pearl"))
+               (buffer-string))))
+    (should-not (string-match-p "saved query" src))))
+
 (provide 'test-pearl-naming)
 ;;; test-pearl-naming.el ends here