From a667efa85a05ac7972ced8f3db1848521ce0da4a Mon Sep 17 00:00:00 2001
From: kshitijk4poor <82637225+kshitijk4poor@users.noreply.github.com>
Date: Thu, 3 Sep 2026 04:54:04 +0530
Subject: [PATCH] test(gateway): drop the stale restore-path section from the
 salvaged test module

---
 tests/gateway/test_transcript_read_failure_100788.py | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/tests/gateway/test_transcript_read_failure_100788.py b/tests/gateway/test_transcript_read_failure_100788.py
index 1234831620..b4dd6c3708 100644
--- a/tests/gateway/test_transcript_read_failure_100788.py
+++ b/tests/gateway/test_transcript_read_failure_100788.py
@@ -14,9 +14,9 @@ model happily answered as if nothing had ever been discussed.
 Two guarantees under test:
   A. ``load_transcript`` raises ``TranscriptReadError`` on a read failure,
      while a genuinely empty session still returns ``[]``.
-  B. The gateway restore path degrades loudly: history stays empty, and a
-     per-turn ephemeral notice is queued telling the model the history
-     exists but is unreadable.
+  B. Slash-command handlers that read the transcript reply with
+     ``HISTORY_UNREADABLE`` instead of raising into the dispatch wrapper
+     (which logs and sends nothing).
 
 Offline: SQLite on tmp_path only, no network.
 """
@@ -74,11 +74,6 @@ class TestLoadTranscriptReadFailure:
         assert store.load_transcript("nope") == []
 
 
-# --------------------------------------------------------------------------
-# B. restore path: empty history + a degraded-history notice
-# --------------------------------------------------------------------------
-
-
 # --------------------------------------------------------------------------
 # B. slash-command handlers surface the failure instead of dying silently.
 #    Before: the handler raised, base.py's dispatch wrapper logged