Expand HTTP analysis with HAR, Site Map, Inspector, Comparer and Decoder #7

User problem

Captured traffic should be easy to search, understand, compare and reuse within one browser workbench.

Acceptance criteria

• Search URLs, headers and bodies and filter history by method, status and resource type.
• Import/export HAR with validation and bounded response bodies.
• Record outgoing Builder, Repeater, Runner and credential-comparison requests in HTTP History.
• Group recorded endpoints by origin, method and path in Site Map.
• Inspect repeated fields, exact JSON numeric tokens, headers and cookie attributes.
• Compare requests/responses with a line diff and optional JSON formatting.
• Decode/encode JSON, URL, Base64, hex and HTML entities; inspect JWTs and compute SHA-256/SHA-512 hashes locally.

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

Node tests cover HAR validation, line diff, codecs/hashes, endpoint grouping and exact-value inspection. Brave integration verifies the tool workflow and API send history.

Relevant source

workbench.js, workflow.js, workflow-ui.js, dashboard.js, tests/workbench.test.js, tests/workflow.test.js

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.