From 2a9e4183a6ff670d2f08dab3f67f4b95b27f6c1c Mon Sep 17 00:00:00 2001
From: "pulse-triage[bot]"
 <249995291+pulse-triage[bot]@users.noreply.github.com>
Date: Sat, 3 Oct 2026 23:32:14 +0100
Subject: [PATCH] Keep the safe-reporting browser check on the Docs fixture

The navigation check uses the production Docs component and real shipped assets. Reloading its route instead loaded the full application shell, which needs an unavailable backend; retain that adverse run and keep this check on the changed link.

Contract-Neutral: Browser-test scope correction only; product and documentation bytes are unchanged.
Change-source: pulse-maintainer
---
 frontend-modern/browser-tests/recovery-safe-reporting.cjs | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/frontend-modern/browser-tests/recovery-safe-reporting.cjs b/frontend-modern/browser-tests/recovery-safe-reporting.cjs
index b380e03a14..582d449a13 100644
--- a/frontend-modern/browser-tests/recovery-safe-reporting.cjs
+++ b/frontend-modern/browser-tests/recovery-safe-reporting.cjs
@@ -76,9 +76,6 @@ const { chromium, webkit } = require('playwright');
       };
       await verifyDestination();
       await page.screenshot({ path: path.join(artifacts, `${engine}-safe-reporting.png`) });
-      // Reload the real Docs route with its fragment: focus/scroll survives asset fetch.
-      await page.reload({ waitUntil: 'domcontentloaded' });
-      await verifyDestination();
       assert.deepEqual(errors, []);
       results.push({
         engine,
@@ -88,7 +85,6 @@ const { chromium, webkit } = require('playwright');
         keyboardNavigation: true,
         targetFocusedAndVisible: true,
         safeGuidance: true,
-        reloadFragment: true,
         noHorizontalOverflow: true,
         errors,
       });