Adjustment to the request debug view functionality

README.md

@@ -30,11 +30,26 @@ The build recreates `dist/chromium` and `dist/firefox` from the same source.
 Do not edit files under `dist` directly. Both targets use Manifest V3, with a
 Chromium service worker and Firefox background scripts. The build composes classic
 factory modules from `scripts/sources.cjs` into one isolated IIFE per execution
-context. It serializes `src/content/styles/redwood.css` at build time. There is no
+context. It serializes `src/content/styles/redwood.css` followed by the scoped
+`src/features/debug/styles.css` at build time. There is no
 runtime module loader, browser-side eval, ES-module requirement or new dependency.
 
 ## Tests and Maintenance
 
+Product HTTP requests appear in Debug Requests (Ctrl+D) as soon as they start.
+Each entry identifies the opportunity and page offset, stays `running` while
+waiting for headers or the response body, and updates with HTTP status, response,
+duration or error. Cache hits do not create HTTP entries. Product diagnostics
+mask authorization and sensitive response headers before messaging the source
+tab/frame; this change adds no timeout, retry or authentication behavior.
+
+Debug tabs group Authentication, Opportunities, Products, AI and Consumption
+requests; unknown request types appear under Other. Only categories with entries
+are shown. All preserves the complete timeline. Every tab sorts by request start
+time, retaining original request IDs and showing start times in collapsed rows.
+Counts and running states update without changing the selected category or
+collapsing expanded details. Use arrow keys, Home and End to navigate the tabs.
+
 ```bash
 npm test
 npm run check