BaaRai d8f47d4359 Traffic ingest: capture operator browsing via a browser extension ...

Closes #33. The MITM proxy only sees the agent's own actions, so
anything behind a human gate (signup captcha, email OTP, 2FA, SSO)
left the authenticated surface dark. The operator's browser becomes a
capture source instead:

- traffic: exported RecordExternal storing an externally captured
  exchange through the same spill/blob/FTS path as proxy traffic
  (insert logic shared with record()); rejects unparsable URLs and
  empty methods
- server: POST /api/traffic/ingest inside the authenticated API group,
  batch capped at 50 entries, bodies truncated at 256 KiB, per-entry
  ingested/failed counts
- extension/: Manifest V3 Chrome/Edge extension driving the
  chrome.debugger Network domain on the chosen tab, batching text
  exchanges to the ingest endpoint with the operator's URL + JWT in
  chrome.storage.local; binary bodies skipped; flush on batch/stop
- tests for both layers, README section

2026-10-11 14:53:08 +02:00

..

background.js

Traffic ingest: capture operator browsing via a browser extension

2026-10-11 14:53:08 +02:00

manifest.json

Traffic ingest: capture operator browsing via a browser extension

2026-10-11 14:53:08 +02:00

popup.html

Traffic ingest: capture operator browsing via a browser extension

2026-10-11 14:53:08 +02:00

popup.js

Traffic ingest: capture operator browsing via a browser extension

2026-10-11 14:53:08 +02:00