Add local WebSocket frame inspection, filtering and export #5

User problem

Developers and security testers need to inspect browser WebSocket traffic alongside HTTP requests.

Acceptance criteria

• Record sent and received frames while a browser tab is attached.
• Display direction, socket URL, opcode and payload; label binary frames as base64.
• Bound storage to 1,000 frames and 20,000 characters per frame, with truncation indication.
• Filter messages/URLs, inspect selected payloads, and open them in Decoder.
• Save frames locally and include them in exports/full workspace backups.
• Observe traffic without pausing or injecting WebSocket messages.

Implementation status

Implemented and verified in PR #1 on feat/v1.1-workbench. PR #1 was merged into main on 2026-10-03, merge commit eeb65009fa6e343cf6dd1f67386be0afc5bbb3e5. GitHub automatically closed this issue as completed through the PR's closing reference. The source changes are now on main; the Chrome Web Store release remains pending.

Verification

The Brave integration uses a local WebSocket fixture and verifies real sent and received messages, persistence and restore.

Relevant source

dashboard.js, lab-ui.js, dashboard.html, tests/browser-integration.mjs

Related v1.1 work is tracked through PR #1. Follow-up improvements or bugs should use their own issue and PR.

Completion record

The implementation commits are 7b76001, 3ee1668, 4f1d89c, 504051e, and test follow-up 619736d. Relevant verification is described above and in PR #1. All 29 Node regressions and JavaScript syntax checks pass; GitHub CI passes on Node 22. The workbench/browser features were checked with isolated local HTTP/WebSocket fixtures; shortcut labels were also checked for Mac/Windows/Linux platforms. The maintainer merged PR #1, and GitHub closed this issue automatically; new bugs or follow-up scope should use a separate issue, or reopen this one if its original criteria fail.