Hartmut
4a5edeef3e
CI / Unit Tests (pull_request) Successful in 5m46s
CI / Lint (pull_request) Failing after 3m49s
CI / E2E Tests (pull_request) Has been skipped
CI / Fresh-Linux Docker Deploy (pull_request) Has been skipped
CI / Assistant Split Regression (pull_request) Failing after 35s
CI / Architecture Guardrails (pull_request) Failing after 2m14s
CI / Typecheck (pull_request) Successful in 4m22s
CI / Build (pull_request) Has been skipped
CI / Release Images (pull_request) Has been skipped
- @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>
76 lines
2.1 KiB
Markdown
76 lines
2.1 KiB
Markdown
# Nexus
|
|
|
|
## Ziel
|
|
|
|
Nexus ist ein Ressourcenplanungs- und Projektbesetzungs-Tool fuer eine 3D-Produktionsumgebung. Der aktuelle Produktkern umfasst Timeline-Planung, Kapazitaets- und Budgetsicht, Rollenmanagement, Blueprint-basierte dynamische Felder, Skill-Matrix-Workflows und einen AI-unterstuetzten Staffing-/Profilbereich.
|
|
|
|
## Tech Stack
|
|
|
|
- TypeScript mit strikten Compiler-Einstellungen
|
|
- Next.js 15 App Router
|
|
- tRPC v11
|
|
- PostgreSQL via Prisma
|
|
- Auth.js v5 mit Argon2-basierter Passwortlogik
|
|
- pnpm Workspaces + Turborepo
|
|
- Tailwind CSS v4
|
|
- SSE/Redis-basierte Realtime-Infrastruktur
|
|
- Vitest und Playwright
|
|
|
|
## Monorepo-Struktur
|
|
|
|
```text
|
|
nexus/
|
|
├── apps/web
|
|
├── packages/shared
|
|
├── packages/db
|
|
├── packages/engine
|
|
├── packages/staffing
|
|
├── packages/application
|
|
├── packages/api
|
|
└── packages/ui
|
|
```
|
|
|
|
## Engineering-Regeln
|
|
|
|
- Geld immer als Integer-Cents speichern
|
|
- Prisma-Enums und JSONB-Felder an Paketgrenzen explizit casten
|
|
- Nullable FKs defensiv behandeln
|
|
- Nach Prisma-Schema-Aenderungen Client regenerieren und den Dev-Server sauber neu starten
|
|
- Keine spekulativen Abstraktionen
|
|
|
|
## Quality Gates
|
|
|
|
- `pnpm test:unit`
|
|
- `pnpm --filter @nexus/web exec tsc --noEmit`
|
|
- `pnpm lint`
|
|
|
|
## Dokumente
|
|
|
|
- Einstiegspunkt: [docs/README.md](docs/README.md)
|
|
- Aktiver Backlog: [docs/product-roadmap.md](docs/product-roadmap.md)
|
|
- Estimating-Design: [docs/estimating-extension-design.md](docs/estimating-extension-design.md)
|
|
- Historische Entscheidungen: [LEARNINGS.md](LEARNINGS.md)
|
|
|
|
## Routing-Regeln Fuer Agenten
|
|
|
|
**Parallel dispatch** nur wenn alle Bedingungen gelten:
|
|
|
|
- 3+ unabhaengige Aufgaben oder Domaenen
|
|
- kein geteilter State
|
|
- klare Dateigrenzen ohne Ueberschneidung
|
|
|
|
**Sequential dispatch** sobald eine Bedingung gilt:
|
|
|
|
- Tasks haben Abhaengigkeiten
|
|
- gemeinsame Dateien erzeugen Merge-Konflikt-Risiko
|
|
- Scope ist noch unklar
|
|
|
|
**Background dispatch** fuer:
|
|
|
|
- Recherche oder Analyse ohne Datei-Aenderungen
|
|
- Aufgaben, deren Ergebnis den aktiven Implementierungsfluss nicht blockiert
|
|
|
|
## Learnings
|
|
|
|
Wichtige Entscheidungen und Problemloesungen werden zentral in [LEARNINGS.md](LEARNINGS.md) festgehalten.
|