Hartmut
29235e3208
CI / Architecture Guardrails (pull_request) Successful in 2m21s
CI / Typecheck (pull_request) Successful in 2m50s
CI / Assistant Split Regression (pull_request) Successful in 4m35s
CI / Lint (pull_request) Successful in 4m46s
CI / Build (pull_request) Successful in 6m41s
CI / Unit Tests (pull_request) Successful in 7m59s
CI / E2E Tests (pull_request) Successful in 5m48s
CI / Fresh-Linux Docker Deploy (pull_request) Successful in 6m25s
CI / Release Images (pull_request) Has been skipped
The Phase 1 codemod only scanned .ts/.tsx/.js/.mjs/.cjs/.json, so two
shell scripts that reference workspace packages stayed pointing at the
old `@capakraken/*` names. The dev container's entrypoint then printed
"No projects matched the filters in /app" on every pnpm --filter call,
the app never bound to port 3100, and Fresh-Linux Docker Deploy red on
run 154.
- tooling/docker/app-dev-start.sh: pnpm --filter @capakraken/{db,web}
→ @nexus/{db,web} (5 occurrences); /tmp/capakraken-dev-home → /tmp/
nexus-dev-home
- scripts/stop.sh: /tmp/capakraken-dev.pid → /tmp/nexus-dev.pid
Deferred to Phase 3 (these reference live infrastructure, not package
names): scripts/harden-postgres.sh DB_USER/DB_NAME defaults, restart.sh
volume names capakraken_node_modules/_next, scripts/start.sh
pg_isready -U capakraken -d capakraken.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>