chore: align migrations, docs, and frontends with crewli.app setup

- Replace dated migrations with ordered 2026_04_07_* chain; fold users update into base migration
- Update OrganisationScope, AppServiceProvider, seeders, api routes, and .env.example
- Refresh Cursor rules, CLAUDE.md, Makefile, README, and docs (API, SCHEMA, SETUP)
- Adjust admin/app/portal HTML, packages, api-client, events types, and theme config
- Update docker-compose and VS Code settings; remove stray Office lock files from resources

Made-with: Cursor

README.md

@@ -1,10 +1,10 @@
-# EventCrew
+# Crewli
 
 Multi-tenant SaaS platform for **event and festival operations**: planning, people, accreditation, artist advancing, volunteer shifts, briefings, and show-day tooling (Mission Control). The backend is a **JSON-only** Laravel API; all user interfaces are **Vue 3** single-page apps.
 
 ---
 
-## What EventCrew covers
+## What Crewli covers
 
 - **Organisations & events** — Multi-tenant data with organisation-scoped access; events move through a defined lifecycle (draft → published → registration → buildup → show day → teardown → closed).
 - **Festival structure** — Sections, time slots, shifts, assignments, claiming/approval flows for volunteers and crew.
@@ -45,7 +45,7 @@ All apps talk to the API over **CORS** with **Laravel Sanctum** tokens.
 ## Project structure
 
 ```
-event-crew/
+crewli/
 ├── api/                 # Laravel 12 REST API (JSON only)
 ├── apps/
 │   ├── admin/           # Super Admin SPA
@@ -94,7 +94,20 @@ Detailed setup: **[docs/SETUP.md](docs/SETUP.md)**.
 | Portal | http://localhost:5175 | `FRONTEND_PORTAL_URL` |
 | Mailpit | http://localhost:8025 | Local mail capture |
 
-Production hostnames are placeholders until you deploy; configure `config/cors.php` via `.env`.
+### Production (crewli.app)
+
+**Domains:** **`crewli.app`** is this product (API + organizer/admin/portal SPAs, transactional email from the app, seeds, etc.). **`crewli.nl`** is reserved for a future **public marketing site** only — do not point this codebase’s `APP_URL`, CORS, Sanctum, or app mail at `crewli.nl`.
+
+Typical layout (configure the same values in `api/.env` — see `api/.env.example`):
+
+| Service | URL | Env variable |
+|---------|-----|----------------|
+| API | `https://api.crewli.app` | `APP_URL` |
+| Admin | `https://admin.crewli.app` | `FRONTEND_ADMIN_URL` |
+| Organizer | `https://app.crewli.app` | `FRONTEND_APP_URL` |
+| Portal | `https://portal.crewli.app` | `FRONTEND_PORTAL_URL` |
+
+Frontends: set `VITE_API_URL=https://api.crewli.app/api/v1` in each app’s env for production builds. `SANCTUM_STATEFUL_DOMAINS` must list the **hostnames only** of the three SPAs (e.g. `admin.crewli.app,app.crewli.app,portal.crewli.app`).
 
 ---
 
@@ -118,7 +131,7 @@ make db-shell
 
 | Resource | Contents |
 |----------|----------|
-| [resources/design/](resources/design/) | **Canonical product specs** — place design documents here (often Word). Referenced by `.cursor` as source of truth for features and data model. Expected names include `EventCrew_Design_Document_v1.3.docx`, `EventCrew_Dev_Guide_v1.0.docx`, `EventCrew_Start_Guide_v1.0.docx` (adjust versions if you update files). |
+| [resources/design/](resources/design/) | **Canonical product specs** — place design documents here (often Word). Referenced by `.cursor` as source of truth for features and data model. Expected names include `Crewli_Design_Document_v1.3.docx`, `Crewli_Dev_Guide_v1.0.docx`, `Crewli_Start_Guide_v1.0.docx` (adjust versions if you update files). |
 | [.cursor/ARCHITECTURE.md](.cursor/ARCHITECTURE.md) | System diagram, apps, multi-tenancy, roles, event lifecycle, API route map, core schema overview (summarises `resources/design` when present) |
 | [.cursor/instructions.md](.cursor/instructions.md) | Quick reference, phased roadmap, module build order |
 | [.cursor/rules/](.cursor/rules/) | Workspace, Laravel, Vue, testing conventions |