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>

samples/Dispov2/plan-utilization-categories.md

@@ -6,22 +6,23 @@
 
 ## Problem
 
-The chargeability report categorizes all work into utilization buckets. Currently CapaKraken projects have no utilization classification. Every project needs a utilization category so that hours booked against it flow into the correct reporting bucket.
+The chargeability report categorizes all work into utilization buckets. Currently Nexus projects have no utilization classification. Every project needs a utilization category so that hours booked against it flow into the correct reporting bucket.
 
 ## Utilization Categories
 
 From the Dispo Categories file (adapted to ACN naming):
 
-| Short | Name | Description |
-|---|---|---|
-| Chg | Chargeable | Billable client project work |
-| BD | Business Development | Sales, proposals, presales activities |
-| MD&I | Market Development and Initiative | R&D, innovation, market development |
-| M&O | Management and Operations | Internal admin, management overhead |
-| PD&R | Personal Development and Recruitment | Training, hiring, onboarding |
-| Absence | Absence & Non Standard | Reduces Standard Available Hours: vacation, illness, non-standard leave |
+| Short   | Name                                 | Description                                                             |
+| ------- | ------------------------------------ | ----------------------------------------------------------------------- |
+| Chg     | Chargeable                           | Billable client project work                                            |
+| BD      | Business Development                 | Sales, proposals, presales activities                                   |
+| MD&I    | Market Development and Initiative    | R&D, innovation, market development                                     |
+| M&O     | Management and Operations            | Internal admin, management overhead                                     |
+| PD&R    | Personal Development and Recruitment | Training, hiring, onboarding                                            |
+| Absence | Absence & Non Standard               | Reduces Standard Available Hours: vacation, illness, non-standard leave |
 
 Notes from the Dispo file:
+
 - "Absent" and "Not available" are merged into "Absence & Non Standard"
 - "Unassigned" hours are calculated automatically (SAH minus all categorized hours)
 - Categories follow ACN naming convention
@@ -58,6 +59,7 @@ model Project {
 ```
 
 Why on Project (not on Allocation/Assignment):
+
 - The Dispo model maps categories to projects, not to individual time entries
 - A project is either "Chargeable" or "Business Development" — the category is a project-level attribute
 - Hours assigned to a project inherit the project's utilization category for reporting
@@ -69,7 +71,7 @@ Why on Project (not on Allocation/Assignment):
 
 interface UtilizationCategory {
   id: string;
-  code: string;      // "Chg", "BD", "MD&I", "M&O", "PD&R", "Absence"
+  code: string; // "Chg", "BD", "MD&I", "M&O", "PD&R", "Absence"
   name: string;
   description?: string;
   sortOrder: number;
@@ -82,13 +84,13 @@ interface UtilizationCategory {
 
 Location: `packages/api/src/router/utilization-category.ts`
 
-| Procedure | Access | Description |
-|---|---|---|
-| `list` | protected | Returns all active categories (sorted) |
-| `getById` | protected | Single category |
-| `create` | admin | Create new category |
-| `update` | admin | Edit code, name, description, sort order |
-| `deactivate` | admin | Soft-delete |
+| Procedure    | Access    | Description                              |
+| ------------ | --------- | ---------------------------------------- |
+| `list`       | protected | Returns all active categories (sorted)   |
+| `getById`    | protected | Single category                          |
+| `create`     | admin     | Create new category                      |
+| `update`     | admin     | Edit code, name, description, sort order |
+| `deactivate` | admin     | Soft-delete                              |
 
 ## UI
 
@@ -109,6 +111,7 @@ Location: `packages/api/src/router/utilization-category.ts`
 ### Chargeability Report
 
 Hours are bucketed by looking up `project.utilizationCategory.code`:
+
 - `Chg` hours → chargeability numerator
 - `BD` hours → business development column
 - `MD&I` hours → market development column