Kann ich One Place vibecoden?

Build me a scheduled personal property monitoring agent, the honest consolation
build for One Place: it watches the sources I configure, it does not rebuild a
live nationwide real-estate index. Requirements:

- Node + Express + better-sqlite3 on localhost:4920, with a small web UI for saved
  searches, matches, and lead notes.
- Saved searches live in SQLite: name, source URLs, natural-language criteria, hard
  filters, cadence, email recipients, and last-run time.
- A node-cron runner wakes on each cadence, fetches configured source/search pages with
  Playwright, and stores raw HTML snapshots for debugging.
- Send cleaned listing HTML to an LLM API key from .env and extract strict JSON: title,
  price, currency, surface, rooms, location text, description, image URLs, source URL, and
  confidence.
- Match each extracted listing against the saved search criteria with deterministic
  filters first, then an LLM yes/no explanation for fuzzy preferences like renovation
  potential or sea view.
- Store listings and match decisions in SQLite, dedupe by canonical URL first and fuzzy
  title+price+surface+location second; keep price-change history.
- Email new matches via Resend or SMTP creds in .env, including the match reason, key
  fields, source link, and unsubscribe/disable link for that saved search.
- Include an MCP server exposing tools: list_saved_searches, run_search_now,
  get_recent_matches, explain_match, update_search, and add_lead_note, so Claude/Codex can
  operate it from chat.
- No accounts, no telemetry, binds to localhost only. Out of scope: nationwide coverage,
  anti-bot arms races, paid data resale, mobile apps, and collaborative CRM.
- README: crawler ethics, robots/terms warning, required API/email keys, how to run the
  scheduler, and how to connect the MCP server.

Antworte mir auf Deutsch. Oberfläche, Kommentare und README auf Deutsch, alle Bezeichner wie Tabellen, Spalten, Variablen, Routen und Dateinamen bleiben Englisch.