3 Commits

Author	SHA1	Message	Date
Hartmut	4a5edeef3e	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
Hartmut	0b330fd344	test(web/e2e): verify root redirect via HTTP not Chromium navigation ... Chromium on the QNAP act_runner intermittently raises ERR_CONNECTION_ REFUSED on page.goto('/') even when curl on the same pinned IP returns 307 a second earlier and the other four smoke tests (api/health, /auth/signin, login, nav) all pass against the same container. The smoke suite has blocked release-images on two successive docker-deploy failures (bee5bbf, e2982a8) and a shell-level suite retry didn't help — the Chromium refusal is reproducible per run. Switch this one test to Playwright's HTTP request API with maxRedirects: 0 and assert on status + Location. Semantically equivalent (it verifies middleware wires / to /auth/signin) and bypasses whatever Chromium-specific quirk is refusing the navigation.	2026-04-13 06:44:39 +02:00
Hartmut	1d02afddfd	ci(e2e): add Playwright smoke tests to deploy-test workflow ... Completes Epic #37 remaining scope: - playwright.ci.config.ts — targets localhost:3100 (already-running Docker app), testMatch restricted to smoke.spec.ts, HTML report on failure - e2e/smoke.spec.ts — 5 tests: health endpoint, unauth redirect, signin page render, admin login redirect, app shell nav visible - deploy-test.yml — seed admin user via docker exec, setup Node 20, install Playwright 1.49 + Chromium, run smoke tests, upload report artifact on failure Co-Authored-By: claude-flow <ruv@ruv.net>	2026-04-02 23:25:12 +02:00