Can I vibecode TripIt Pro?

Build me a personal trip organiser that reads my booking emails, to replace TripIt Pro. Requirements:

- Node.js 22 + TypeScript: a Fastify server with server-rendered pages (Eta) and a little vanilla JS, laid out for a
  phone screen. `npm start` serves http://127.0.0.1:4960.
- Storage: better-sqlite3 in ./data/trips.db: trips, and items (flight, hotel, car, train, activity) with local start
  and end times plus an IANA zone, the raw email, the parsed JSON and a status of needs-review or confirmed.
- Intake: `imapflow` checks one mailbox folder called Trips every 5 minutes (IMAP_HOST, IMAP_USER and
  IMAP_PASSWORD in .env, an app password). I forward confirmations there; read the body and the first PDF (`unpdf`).
- Parsing: send the email text to an OpenAI-compatible chat endpoint (LLM_BASE_URL, LLM_MODEL, LLM_API_KEY in .env;
  a local Ollama URL must work) and ask for JSON that matches a `zod` schema. Anything that fails validation goes
  under "Could not read". Show each parsed item beside its source email so I can check and edit it.
- Times: airports from the OurAirports CSV downloaded once into ./data/, zones from `tz-lookup`, dates with `luxon`.
  A flight shows departure and arrival in each airport's local time, plus the duration.
- Trips: group items whose dates fall within 2 days of each other; a trip page with a day-by-day timeline,
  confirmation numbers one tap away, and a print view.
- Calendar: a read-only .ics feed at /calendar/<CALENDAR_TOKEN>.ics (`ics` package) for my phone calendar.
- Flight alerts: a FlightStatusProvider interface with one implementation (AeroDataBox through RapidAPI, key in
  .env). Poll only flights departing within 24 hours, at most every 15 minutes, and push through ntfy (NTFY_URL,
  NTFY_TOPIC) for delays of 15 minutes or more, gate or terminal changes and cancellations. Add a "leave now" push
  at departure minus a home-to-airport time and a buffer that I set on a settings page.
- Single user. No accounts, no telemetry, local-first. Outbound calls: IMAP, my LLM endpoint, the flight API, ntfy.
- Out of scope: seat and fare tracking, airport maps, loyalty points, sharing, native apps, Gmail or Outlook sync.
- README: creating the IMAP app password and a forwarding rule, running Ollama instead of a hosted model, how to
  reach the calendar feed from a phone, and a note that email text goes to whichever LLM you configure.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.