rename(phase 1): CapaKraken → Nexus across code, UI, docs, CI

- @capakraken/* → @nexus/* across 12 packages (root + 11 workspaces),
  1551 import lines migrated via codemod
- User-visible brand strings renamed (emails, page titles, PWA
  manifest, mobile header, MFA backup-codes header, tooltips, signin
  page, invite page, weekly digest, install prompt)
- TOTP issuer "CapaKraken" → "Nexus" (existing secrets still valid;
  re-enrollment relabels them in users' authenticator apps)
- Function rename: assertCapaKrakenDbTarget → assertNexusDbTarget
- LocalStorage migration shim in apps/web/src/app/layout.tsx copies
  capakraken_* → nexus_* on first load (guarded by nexus_migrated_v1
  sentinel; runs once per browser, then never again)
- Service-worker cache name capakraken-v2 → nexus-v2 with one-time
  caches.delete('capakraken-v2') from the same shim
- Email-domain fixtures @capakraken.{dev,app} → @nexus.{dev,app} in
  seed data, e2e specs, SMTP default fallback
- Dockerfile.dev / Dockerfile.prod / all .github/workflows/*.yml
  pnpm --filter @capakraken/* → @nexus/*
- README, CLAUDE.md, LEARNINGS.md, all docs/*.md, .env.example,
  tooling/deploy/.env.production.example brand sweep

Phase 1 deliberately leaves untouched (handled in Phase 3 cutover):
- PostgreSQL DB name "capakraken" and POSTGRES_USER "capakraken"
- Volume names capakraken_pgdata etc.
- Compose project name "capakraken" / "capakraken-prod"
- db-target-guard default expectedDatabase
- env-var CAPAKRAKEN_EXPECTED_DB_NAME
- Container DNS names in docker-compose.ci.yml

Quality gates green: pnpm typecheck (7/7), pnpm test:unit (7/7),
pnpm lint (0 errors), check:exports/imports/architecture all pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

docs/performance-optimization-review-2026-03-18.md

@@ -6,7 +6,7 @@ Scope: analysis only. No runtime behavior was changed in this pass.
 
 ## Executive Summary
 
-The biggest performance costs in CapaKraken currently come from three patterns:
+The biggest performance costs in Nexus currently come from three patterns:
 
 1. Broad data fetches followed by repeated in-memory filtering/grouping.
 2. Expensive client-side derivations on screens with large datasets, especially Timeline.
@@ -20,11 +20,11 @@ The highest-value optimization target is the Timeline stack. After that, the bes
 
 Relevant files:
 
-- [TimelineContext.tsx](/home/hartmut/Documents/Copilot/capakraken/apps/web/src/components/timeline/TimelineContext.tsx)
-- [TimelineView.tsx](/home/hartmut/Documents/Copilot/capakraken/apps/web/src/components/timeline/TimelineView.tsx)
-- [TimelineResourcePanel.tsx](/home/hartmut/Documents/Copilot/capakraken/apps/web/src/components/timeline/TimelineResourcePanel.tsx)
-- [TimelineProjectPanel.tsx](/home/hartmut/Documents/Copilot/capakraken/apps/web/src/components/timeline/TimelineProjectPanel.tsx)
-- [timeline.ts](/home/hartmut/Documents/Copilot/capakraken/packages/api/src/router/timeline.ts)
+- [TimelineContext.tsx](/home/hartmut/Documents/Copilot/nexus/apps/web/src/components/timeline/TimelineContext.tsx)
+- [TimelineView.tsx](/home/hartmut/Documents/Copilot/nexus/apps/web/src/components/timeline/TimelineView.tsx)
+- [TimelineResourcePanel.tsx](/home/hartmut/Documents/Copilot/nexus/apps/web/src/components/timeline/TimelineResourcePanel.tsx)
+- [TimelineProjectPanel.tsx](/home/hartmut/Documents/Copilot/nexus/apps/web/src/components/timeline/TimelineProjectPanel.tsx)
+- [timeline.ts](/home/hartmut/Documents/Copilot/nexus/packages/api/src/router/timeline.ts)
 
 Observed issues:
 
@@ -43,8 +43,8 @@ Impact:
 
 Relevant files:
 
-- [ChargeabilityReportClient.tsx](/home/hartmut/Documents/Copilot/capakraken/apps/web/src/components/reports/ChargeabilityReportClient.tsx)
-- [chargeability-report.ts](/home/hartmut/Documents/Copilot/capakraken/packages/api/src/router/chargeability-report.ts)
+- [ChargeabilityReportClient.tsx](/home/hartmut/Documents/Copilot/nexus/apps/web/src/components/reports/ChargeabilityReportClient.tsx)
+- [chargeability-report.ts](/home/hartmut/Documents/Copilot/nexus/packages/api/src/router/chargeability-report.ts)
 
 Observed issues:
 
@@ -62,9 +62,9 @@ Impact:
 
 Relevant files:
 
-- [dashboard.ts](/home/hartmut/Documents/Copilot/capakraken/packages/api/src/router/dashboard.ts)
-- [get-chargeability-overview.ts](/home/hartmut/Documents/Copilot/capakraken/packages/application/src/use-cases/dashboard/get-chargeability-overview.ts)
-- [get-overview.ts](/home/hartmut/Documents/Copilot/capakraken/packages/application/src/use-cases/dashboard/get-overview.ts)
+- [dashboard.ts](/home/hartmut/Documents/Copilot/nexus/packages/api/src/router/dashboard.ts)
+- [get-chargeability-overview.ts](/home/hartmut/Documents/Copilot/nexus/packages/application/src/use-cases/dashboard/get-chargeability-overview.ts)
+- [get-overview.ts](/home/hartmut/Documents/Copilot/nexus/packages/application/src/use-cases/dashboard/get-overview.ts)
 
 Observed issues:
 
@@ -80,8 +80,8 @@ Impact:
 
 Relevant files:
 
-- [ResourcesClient.tsx](/home/hartmut/Documents/Copilot/capakraken/apps/web/src/app/(app)/resources/ResourcesClient.tsx)
-- [resource.ts](/home/hartmut/Documents/Copilot/capakraken/packages/api/src/router/resource.ts)
+- [ResourcesClient.tsx](</home/hartmut/Documents/Copilot/nexus/apps/web/src/app/(app)/resources/ResourcesClient.tsx>)
+- [resource.ts](/home/hartmut/Documents/Copilot/nexus/packages/api/src/router/resource.ts)
 
 Observed issues:
 
@@ -97,7 +97,7 @@ Impact:
 
 Relevant files:
 
-- [list-assignment-bookings.ts](/home/hartmut/Documents/Copilot/capakraken/packages/application/src/use-cases/allocation/list-assignment-bookings.ts)
+- [list-assignment-bookings.ts](/home/hartmut/Documents/Copilot/nexus/packages/application/src/use-cases/allocation/list-assignment-bookings.ts)
 
 Observed issues:
 
@@ -112,7 +112,7 @@ Impact:
 
 Relevant schema:
 
-- [schema.prisma](/home/hartmut/Documents/Copilot/capakraken/packages/db/prisma/schema.prisma)
+- [schema.prisma](/home/hartmut/Documents/Copilot/nexus/packages/db/prisma/schema.prisma)
 
 Good coverage already exists for: