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>
2026-05-21 15:10:44 +02:00
parent d9a7ec0338
commit 4a5edeef3e
941 changed files with 24475 additions and 16760 deletions
@@ -8,4 +8,4 @@ Most of this plan has already been implemented:
 - admin system settings for AI configuration
 - AI summary generation and resource detail UI

-Do not use this file as an active backlog. Remaining product work belongs in [docs/product-roadmap.md](/home/hartmut/Documents/Copilot/capakraken/docs/product-roadmap.md), and completed implementation detail is reflected in the codebase and [LEARNINGS.md](/home/hartmut/Documents/Copilot/capakraken/LEARNINGS.md).
+Do not use this file as an active backlog. Remaining product work belongs in [docs/product-roadmap.md](/home/hartmut/Documents/Copilot/nexus/docs/product-roadmap.md), and completed implementation detail is reflected in the codebase and [LEARNINGS.md](/home/hartmut/Documents/Copilot/nexus/LEARNINGS.md).
@@ -12,4 +12,4 @@ Examples that are no longer current:
 - Redis-backed SSE work has already landed
 - Playwright E2E coverage is no longer empty

-Use [product-roadmap.md](/home/hartmut/Documents/Copilot/capakraken/docs/product-roadmap.md) for the active backlog and [v2-architecture-proposal-2026-03-11.md](/home/hartmut/Documents/Copilot/capakraken/research/v2-architecture-proposal-2026-03-11.md) for the still-relevant strategic direction.
+Use [product-roadmap.md](/home/hartmut/Documents/Copilot/nexus/docs/product-roadmap.md) for the active backlog and [v2-architecture-proposal-2026-03-11.md](/home/hartmut/Documents/Copilot/nexus/research/v2-architecture-proposal-2026-03-11.md) for the still-relevant strategic direction.
@@ -1,3 +1,3 @@
 # Archived Proposal Note

-The CGI workbook analysis and implementation proposal were merged into [estimating-extension-design.md](/home/hartmut/Documents/Copilot/capakraken/docs/estimating-extension-design.md) so the estimating work now has one canonical document.
+The CGI workbook analysis and implementation proposal were merged into [estimating-extension-design.md](/home/hartmut/Documents/Copilot/nexus/docs/estimating-extension-design.md) so the estimating work now has one canonical document.
@@ -1,3 +1,3 @@
 # Archived Mapping Note

-The field mapping table was merged into [estimating-extension-design.md](/home/hartmut/Documents/Copilot/capakraken/docs/estimating-extension-design.md) so the estimating design, workbook analysis, and implementation plan live in one canonical file.
+The field mapping table was merged into [estimating-extension-design.md](/home/hartmut/Documents/Copilot/nexus/docs/estimating-extension-design.md) so the estimating design, workbook analysis, and implementation plan live in one canonical file.
@@ -16,4 +16,4 @@ Still conceptually relevant, but no longer the canonical backlog:
 - staffing suggestion scalability
 - index strategy for larger datasets

-Use [product-roadmap.md](/home/hartmut/Documents/Copilot/capakraken/docs/product-roadmap.md) for active prioritization and keep this file only as archive context.
+Use [product-roadmap.md](/home/hartmut/Documents/Copilot/nexus/docs/product-roadmap.md) for active prioritization and keep this file only as archive context.
@@ -8,4 +8,4 @@ That work is now only partially relevant as an archive:
 - several sorting/view-state pieces were implemented
 - Blueprints parity still appears open

-The active backlog now lives in [docs/product-roadmap.md](/home/hartmut/Documents/Copilot/capakraken/docs/product-roadmap.md).
+The active backlog now lives in [docs/product-roadmap.md](/home/hartmut/Documents/Copilot/nexus/docs/product-roadmap.md).
@@ -2,7 +2,7 @@

 This sprint plan mixed active refactor work with implementation mechanics that are now stale.

-The still-relevant backlog from this document is tracked centrally in [product-roadmap.md](/home/hartmut/Documents/Copilot/capakraken/docs/product-roadmap.md):
+The still-relevant backlog from this document is tracked centrally in [product-roadmap.md](/home/hartmut/Documents/Copilot/nexus/docs/product-roadmap.md):

 - widget config typing and layout versioning
 - registry-driven dashboard rendering
@@ -6,24 +6,26 @@ Alle Quality Gates bestanden. Keine kritischen Probleme. Zwei Minor-Empfehlungen

 ## Quality Gates

-| Gate | Status | Details |
-|------|--------|---------|
-| Engine Tests | ✅ | 283/283 (19 files) |
-| Staffing Tests | ✅ | 37/37 (3 files) |
-| API Tests | ✅ | 209/209 (21 files) |
-| Application Tests | ✅ | 67/67 (15 files) |
-| TypeScript (web) | ✅ | 0 errors (excl. BlueprintFieldEditor TS2589) |
-| TypeScript (api) | ✅ | 0 errors |
+| Gate              | Status | Details                                      |
+| ----------------- | ------ | -------------------------------------------- |
+| Engine Tests      | ✅     | 283/283 (19 files)                           |
+| Staffing Tests    | ✅     | 37/37 (3 files)                              |
+| API Tests         | ✅     | 209/209 (21 files)                           |
+| Application Tests | ✅     | 67/67 (15 files)                             |
+| TypeScript (web)  | ✅     | 0 errors (excl. BlueprintFieldEditor TS2589) |
+| TypeScript (api)  | ✅     | 0 errors                                     |

 ## Code-Review-Checkliste

 ### Architektur
+
 - [x] Keine zirkulaeren Abhaengigkeiten — `api → engine/shared/db` (erlaubt)
 - [x] `engine` und `staffing` unveraendert, keine DB-Imports
 - [x] Neuer Router `computationGraph` in `index.ts` registriert
 - [x] Keine SSE-Events noetig (read-only Feature, keine Mutations)

 ### TypeScript & Typsicherheit
+
 - [x] `any`-Types nur an `react-force-graph-3d`-Grenzen mit `eslint-disable` Kommentar (6 Stellen)
 - [x] Prisma-Enums gecastet: `pa.status as unknown as string` + `as Parameters<typeof computeBudgetStatus>[2]`
 - [x] JSONB-Feld gecastet: `commercialTerms as { contingencyPercent?: number; ... } | null`
@@ -31,17 +33,20 @@ Alle Quality Gates bestanden. Keine kritischen Probleme. Zwei Minor-Empfehlungen
 - [x] `exactOptionalPropertyTypes` beachtet: `...(formula ? { formula } : {})` Pattern

 ### Datenbank & Prisma
+
 - [x] Keine Schema-Aenderungen — rein lesende Queries
 - [x] Geldbetraege in Integer-Cents: `lcrCents`, `dailyCostCents`, `budgetCents` etc.
 - [x] Kein Seed noetig (kein neues Modell)

 ### UI & Komponenten
+
 - [x] `"use client"` Direktive gesetzt
 - [x] Three.js via `dynamic(() => import(...), { ssr: false })` — kein SSR-Problem
 - [x] Neue Seite in AppShell-Navigation ergaenzt ("Computation Graph" unter Analytics)
 - [x] Opake Hintergruende: `bg-zinc-50`, `bg-zinc-900/95` (95% ist akzeptabel fuer Tooltip)

 ### Sicherheit
+
 - [x] Beide Procedures nutzen `controllerProcedure` (ADMIN + MANAGER + CONTROLLER)
 - [x] Keine Raw-Queries — nur Prisma `findMany`/`findUniqueOrThrow`
 - [x] Keine sensiblen Daten im Response — nur berechnete Werte und Formeln
@@ -49,11 +54,12 @@ Alle Quality Gates bestanden. Keine kritischen Probleme. Zwei Minor-Empfehlungen
 ## Gefundene Probleme

 ### Kritisch
+
 Keine.

 ### Minor

-1. **Duplizierte Types** — `GraphNode`, `GraphLink`, `Domain` sind sowohl in `packages/api/.../computation-graph.ts` als auch `apps/web/.../domain-colors.ts` definiert. Funktioniert (tRPC inferiert die Typen), aber bei Aenderungen muss man beide Stellen anpassen. Empfehlung: Types nach `@capakraken/shared` verschieben wenn sie stabil sind.
+1. **Duplizierte Types** — `GraphNode`, `GraphLink`, `Domain` sind sowohl in `packages/api/.../computation-graph.ts` als auch `apps/web/.../domain-colors.ts` definiert. Funktioniert (tRPC inferiert die Typen), aber bei Aenderungen muss man beide Stellen anpassen. Empfehlung: Types nach `@nexus/shared` verschieben wenn sie stabil sind.

 2. **`project.list` Query** — Der Client castet das Ergebnis via `(projectData as any)?.projects ?? (projectData as any)`. Das deutet auf Unsicherheit ueber das Return-Format hin. Sollte nach dem Merge geprueft werden, ob `.projects` oder direkt das Array zurueckkommt.