feat(extension): advanced recording settings for Network Interceptor

[nafees87n]

What

Adds four advanced recording settings to the LTS Network Interceptor, mirroring the classic LTS recorder's "Advanced Options". All ride the existing startNetworkRecording config object (no new message types, no listener change). Chrome + Edge only — Firefox/Safari are unaffected (feature-guarded; no manifest change there).

Story: RQ-3330 (epic RQ-2894)
Contract doc: Confluence — Requestly <> LT network interceptor integration (v34)

Options

Config key	Default	Behavior
disableCache	false	Wipe the HTTP cache for the recorded origin at record start (DevTools "Disable cache" equivalent) — cold first load, no 304/from-cache skeletons. No Cache-Control header injection (would distort recorded traffic).
wipeServiceWorkers	false	Unregister the origin's service workers + clear the Cache API (cacheStorage) they serve from, at record start.
recordAjax	true	true → XHR/Fetch recorded with full bodies+headers (web-sdk, v2). false → XHR/Fetch not recorded at all (suppressed from both the SDK page script and the webRequest path). A yes/no on recording ajax, not a bodies toggle.
requestScope	"all"	"all" → every frame. "top-level" → only main-frame requests (frameId === 0), dropping iframe-originated requests.

The two cache/SW wipes coalesce into one chrome.browsingData.remove call.

Key implementation notes

• Gesture-safe: the wipe is fire-and-forget (never awaited), issued inside the chrome.tabs.create callback, so chrome.sidePanel.open() keeps its user gesture. Verified the panel still opens with both wipes on.
• Feature-guarded: all browsingData access via (chrome as any).browsingData?.remove with a typeof check → clean no-op on Firefox/Safari.
• New permission: browsingData added to manifest.chrome.json + manifest.edge.json only. ⚠️ This re-prompts existing Chrome/Edge users to accept on update. Store-review justification: "browsingData is used solely to clear the recorded site's HTTP/Cache-API cache and service workers at the moment a user starts a network recording, so captured traffic reflects a clean, uncached load."
• requestScope is a string-valued RequestScope enum (wire value stays "all"/"top-level").
• Config fields stay optional in the contract type (defensive defaults), but LTS is expected to send all four explicitly per the user's selection (documented in the Confluence contract).

Caveats (documented)

• disableCache clears the whole-browser HTTP cache (Chrome ignores origins for the cache data type; only cacheStorage is origin-scoped) — a momentary record-start action.
• wipeServiceWorkers + origins may be silently ignored on some Chrome versions (degrades gracefully, best-effort).

Testing

Manually verified all four on a loaded build:

• disableCache → static assets fetched from network, not disk cache
• wipeServiceWorkers → SW unregistered (confirmed via chrome://serviceworker-internals + the browsingData.remove call firing with the right payload in the SW console)
• recordAjax: false → zero xhr/fetch entries; non-ajax resources still captured
• requestScope: "top-level" → iframe requests dropped
• Gesture regression → side panel opens with both wipes enabled

Build is clean (only pre-existing TS7030/circular-dep warnings on listener.ts, unrelated to this change). Harness (test/network-recording-test.html) updated with the four toggles.

🤖 Generated with Claude Code