Should you build your own GetXAPI?

Build me a personal Twitter/X archive tool in Python.

- Use twscrape (pip) for all X access; I will add one or two throwaway
  accounts with `twscrape add_accounts` myself. Never use my real account.
- watchlist.txt holds up to 10 handles, one per line.
- An hourly cron entry point `python fetch.py`: for each handle, pull new
  tweets since the last stored id and upsert into SQLite (tweets: id, handle,
  text, created_at, like_count, retweet_count, is_reply, is_quote).
- Be gentle: shuffle handle order, sleep 5-15s between handles, and back off
  for an hour on repeated failures instead of hammering.
- `python export.py <handle>` writes that handle's archive to JSON and CSV.
- A localhost dashboard (Flask, one page): newest tweets across all handles,
  a per-handle sparkline of tweets per day, and a search box over a SQLite
  full-text index.
- Local only: no cloud, no accounts beyond the burners, no telemetry;
  session data stays in twscrape's own store.
- README: setup, the cron line, and a blunt warning that scraping X breaks
  routinely and burner accounts get flagged; when fetch.py starts failing,
  re-login or swap accounts.
- Explicitly out of scope: posting, DMs, webhooks/streaming, more than ~10
  handles, and anything commercial.