From 16899ae144f63c27f3b5334bb815206ddb986c44 Mon Sep 17 00:00:00 2001 From: teknium1 <127238744+teknium1@users.noreply.github.com> Date: Sun, 21 Jun 2026 11:36:51 -0700 Subject: [PATCH] test(file): update guard assertions for unified display-text message The salvaged #19820 unifies the write_file guard under _is_internal_file_tool_content with the message 'internal read_file display text'. Two tests added to test_file_read_guards.py after the PR branch point still asserted the old 'status text' wording. Update them to match the new (correct, more general) message. --- tests/tools/test_file_read_guards.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/tools/test_file_read_guards.py b/tests/tools/test_file_read_guards.py index ee4e43a8774..8c05413065e 100644 --- a/tests/tools/test_file_read_guards.py +++ b/tests/tools/test_file_read_guards.py @@ -275,7 +275,7 @@ class TestFileDedup(unittest.TestCase): )) self.assertIn("error", result) - self.assertIn("internal read_file status text", result["error"]) + self.assertIn("internal read_file display text", result["error"]) fake.write_file.assert_not_called() @patch("tools.file_tools._get_file_ops") @@ -299,7 +299,7 @@ class TestFileDedup(unittest.TestCase): )) self.assertIn("error", result) - self.assertIn("internal read_file status text", result["error"]) + self.assertIn("internal read_file display text", result["error"]) fake.write_file.assert_not_called() @patch("tools.file_tools._get_file_ops")