The visible feature was only the surface
Screenshots and vague descriptions rarely preserve the sequence, browser evidence, environment, and visual result developers need to reproduce a web application failure.
The system also had to respect concrete constraints. Browser diagnostics and screen recordings can expose sensitive information, while local filtering cannot guarantee that every secret will be recognized. Chrome permission, selected-tab, service-worker, navigation, and storage boundaries must remain understandable during a capture. Email delivery crosses a separate network boundary and must not bundle server credentials or silently transmit evidence.
My role covered product design and browser-extension engineering, with responsibility for capture lifecycle, privacy boundaries, review workflows, and release delivery.
I turned the constraints into boundaries
WXT Manifest V3 side panel, selected-tab recorder, review page, and background capture lifecycle; isolated page instrumentation feeding typed capture contracts; deterministic local privacy filtering and report rendering; extension storage and IndexedDB with local export or explicit Resend delivery through a TanStack Start endpoint.
Capture and filter evidence inside the extension first so downloading remains the default and email delivery is a separate, explicit boundary.
Open an editable review surface before export so users can remove individual steps, diagnostics, and visual artifacts after automated filtering.
Record selected console and network evidence without collecting DOM snapshots, cookies, browser storage, headers, form values, keystrokes, clipboard contents, or audio.
The key decision: Capture evidence locally before defining any sharing path.
The implementation had to prove the model
I delivered the work across the full path: Designed the selected-tab capture, manual-step, stop, review, edit, download, copy, and explicit email journeys. Implemented background session ownership, isolated page instrumentation, cross-origin interruption handling, and persistent evidence storage. Built deterministic filtering for URLs, diagnostic text, supported response bodies, tokens, email addresses, and secret-shaped fields. Created the TanStack Start delivery endpoint, Resend boundary, deterministic broken-app fixture, CI quality gate, and checksummed Chrome release workflow.
The result is concrete: Reporters can preserve reproduction steps, bounded console and network evidence, environment details, and a recording or screenshot in one workflow. Every captured item remains reviewable and removable before it leaves extension-owned storage. Users can export a local Markdown-and-visual bundle or deliberately send a size-bounded report through the configured endpoint. Maintainers can exercise known failures and ship verifiable unpacked Chrome archives with published checksums.
The senior engineering lesson was that solving the visible workflow is only half the job. The architecture must also make constraints, failure modes, evidence, and ownership explicit enough for the next change to remain safe.