Build an event ticketing and registration platform

You are a senior full-stack developer who builds ticketing systems. Build an event ticketing platform with me, phase by phase.

## The platform
- Who creates events: [only us / any organiser who signs up]
- Event types: [concerts, conferences, workshops, sports, online events]
- Seating: [general admission / reserved seats with a seat map]
- Fees: [e.g. 5% platform fee + gateway fee, paid by buyer or organiser]
- Payment gateway: [GATEWAY]
- Tech stack I prefer: [STACK or "you choose"]

## Features
1. Event pages: banner, description, date and time with time zone, venue with map or online link, agenda, speakers or artists, FAQs, organiser info, share buttons.
2. Ticket types: early bird, regular, VIP, group, with quantities, sale windows, per-order limits, promo codes.
3. Seat maps for reserved seating with seats held for [10] minutes during checkout.
4. Checkout: attendee details per ticket (custom questions), payment, e-ticket email and WhatsApp with a unique QR code, add to calendar.
5. Check-in app for staff: scan QR (works offline and syncs), manual search, live entry counts, prevent duplicate entry.
6. Organiser dashboard: create and edit events, sales in real time, attendee list export, messages to attendees, refunds and cancellations, payouts after the event.
7. Discovery: browse events by city, date and category; search.
8. Admin: approve organisers and events, fees, payouts, disputes, reports.

## Ticketing rules
- No overselling: ticket and seat inventory is reserved inside a database transaction; the site must survive a rush when a popular event goes on sale (queue if needed).
- QR codes are signed so they cannot be forged.
- Event JSON-LD (Event, Offer, Place) on every event page.

## Quality rules (apply to every phase)
- Security: prepared statements or an ORM for every query, output escaping, CSRF tokens on every form, passwords hashed with bcrypt or Argon2, rate-limited login, role checks on the server for every admin route, file uploads checked by type and size and stored outside the web root or with random names, secrets only in an .env file.
- Validation: validate every input on the server (and also in the browser for speed). Show clear error messages next to the field that is wrong, and keep what the user already typed.
- Performance: pagination on every list, database indexes on every column used for search, filter or join, lazy-loaded and resized images (WebP), caching for pages that rarely change, no N+1 queries.
- Responsive and accessible: mobile first, works from 360px to wide desktop, proper labels on every form field, keyboard navigation, visible focus, colour contrast of at least 4.5:1, alt text on images.
- SEO: clean URLs, a unique title and meta description per page, canonical tags, Open Graph tags, schema.org JSON-LD where it applies, an XML sitemap and robots.txt.
- Code: small functions with clear names, one responsibility per file, comments only where the reason is not obvious, consistent formatting, no dead code.
- Errors: friendly error pages (404, 500), server errors written to a log, never shown to visitors.
- Deliver with: a README (install steps, .env example, how to create the first admin), database migrations and seed data with realistic sample content, and a deployment checklist.

## How to work with me
Do not write code yet. First reply with:
1. A short summary of what you understood, and anything in the brief that is unclear or contradictory (ask me, do not guess).
2. The final tech stack, with a one-line reason for each choice.
3. The folder and file structure.
4. The full database schema: every table, column, type, index and relation.
5. Every page or screen, and every API endpoint (method, path, who can call it, what it returns).
6. The build plan as numbered phases, each one small enough to finish and test on its own.

Wait for me to reply "go". Then build one phase at a time:
- For every file, give the full path and the complete code. Never write "...", "rest of the code stays the same" or TODO.
- After each phase, tell me how to run it, what to click to test it, and what is still missing. Then wait for me to reply "next".
- If you change a file you already gave me, give the whole updated file again.