Not-found failures say it once, in plain words: grep: pattern not found, callers not found

The ENOENT that 9ns reads from a failure's words came from a tacked-on suffix, grep: no match, not found, definition: nothing found, not found, no shell "x", not found. They now say it once: grep: pattern not found, find: name not found, Callers: callers not found, definition: not found, shell "x" not found (...).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 2 insertions, 2 deletions

diff --git a/test/fs.py b/test/fs.py
index 8047273d..6a9e78f6 100644
--- a/test/fs.py
+++ b/test/fs.py
@@ -622,11 +622,11 @@ def workflow_canary(binary):
             rows = client.read(f'/pane/{grep}/body').decode()
             assert 'a.txt:2' in rows and 'b.txt:2' in rows, rows
             client.remove(f'/pane/{grep}')
-            execute_refused(client, a, 'Grep zzqqnomatch', 'grep: no match')
+            execute_refused(client, a, 'Grep zzqqnomatch', 'grep: pattern not found')
             found = made_by(a, b'Find b.txt\n')
             assert 'b.txt' in client.read(f'/pane/{found}/body').decode()
             client.remove(f'/pane/{found}')
-            execute_refused(client, a, 'Find zzqqnomatch', 'find: no match')
+            execute_refused(client, a, 'Find zzqqnomatch', 'find: name not found')
 
             # A plain word looked at is found in the pane, after its dot.
             client.write(f'/pane/{a}/dot', b'          0           0 ')