Vale construir sua versão de Debriefing?

Build me a local competitor watch that emails me a weekly brief, to replace Debriefing. Requirements:

- Node 22, TypeScript, SQLite via better-sqlite3, Playwright for fetching, node-cron for
  the schedule. CLI only. No accounts, no telemetry, keys in .env.
- competitors.json lists each rival: name, and the URLs that matter (homepage, pricing,
  changelog, careers). Ship it seeded with 3 competitors and 4 URLs each.
- `watch snapshot` fetches every URL with Playwright, strips scripts, styles, nav and
  footer, converts the main content to plain text, and stores it with a SHA-256 hash and
  a timestamp. Skip storage entirely when the hash is unchanged.
- Diff each new snapshot against the previous one as unified text diff. Discard diffs
  under 40 changed characters, and drop lines matching an editable noise.json of regexes
  (dates, cache-busting hashes, view counts, testimonial rotations).
- `watch brief` sends the surviving diffs for the period to Claude or GPT in one call
  and asks for, per competitor: what changed, why it matters, and one suggested response.
  Require a citation back to the exact URL for every claim, and drop any bullet without
  one.
- Render the brief to Markdown in ~/CompetitorBriefs/YYYY-MM-DD.md and send it via SMTP
  from .env. The file is the source of truth, email is just delivery.
- Keep every snapshot and every brief. `watch history <competitor>` prints that rival's
  changes over time, which is the only way a single diff becomes a trend.
- Out of scope: hiring feeds, funding data, traffic estimates, dashboards and any login
  wall. Public pages only, respect robots.txt, one request per URL per run.
- README: setup, a cron line for the weekly run, the per-brief token cost, and a warning
  that month one is mostly tuning noise.json.