feat: user invite flow, deactivate/delete, favicon, dashboard loading fix, admin full-width

- Invite flow: admin can invite users by email with role selection; accept-invite page
  sets password and creates the account; 72-hour token expiry; E2E tests
- User deactivate/reactivate/delete: new tRPC procedures + UI buttons; deactivation
  revokes all active sessions immediately; delete cascades vacation/broadcast records;
  isActive field added via migration 20260402000000_user_isactive
- Auth: block login for inactive users with audit entry
- Favicon: SVG favicon + ICO/PNG fallbacks (16, 32, 180, 192, 512px); manifest updated
- Dashboard: GridLayout dynamic-import loading skeleton prevents blank dark area
  on first login before react-grid-layout chunk is cached
- Admin users: remove max-w-5xl constraint so table uses full page width
- Dev: docker container restart workflow documented in LEARNINGS.md; Prisma generate
  must run inside the container after schema changes (named node_modules volume)

Co-Authored-By: claude-flow <ruv@ruv.net>

LEARNINGS.md

@@ -7,6 +7,22 @@
 
 ## Learnings
 
+### 2026-04-02 | DevOps | Prisma schema changes require container restart
+
+**Problem:** After adding a new column to `schema.prisma` and running `prisma generate` on the host, the running Docker app container still used the old Prisma client (the container's `node_modules` is a named Docker volume, isolated from the host filesystem). Queries referencing the new field (`isActive`) failed at runtime, causing tRPC procedures to return errors.
+
+**Solution:** Always restart the app container after Prisma schema changes:
+```
+docker compose --profile full restart app
+```
+The startup script `tooling/docker/app-dev-start.sh` already runs `prisma generate` + `db:migrate:deploy` on every container start — so a restart is sufficient. No rebuild needed unless `pnpm-lock.yaml` or `Dockerfile.dev` changed.
+
+**Rule:** Prisma schema change checklist:
+1. Edit `packages/db/prisma/schema.prisma`
+2. Write migration SQL in `packages/db/prisma/migrations/<timestamp>_<name>/migration.sql`
+3. Apply migration to the running DB directly (for dev speed): `docker exec capakraken-postgres-1 psql -U capakraken -d capakraken < migration.sql`
+4. `docker compose --profile full restart app` — regenerates Prisma client + runs migrations inside the container
+
 ### 2026-03-13 | Architecture | Dispo v2 chargeability calculator design
 - Pure functions in `packages/engine/src/chargeability/calculator.ts` — no DB imports, all data passed as arguments.
 - `deriveResourceForecast()` takes SAH + assignment slices per month, returns ratio breakdown (Chg/BD/MD&I/M&O/PD&R/Absence/Unassigned).