Hartmut
7cee3b3a97
CI / Architecture Guardrails (pull_request) Successful in 2m54s
CI / Lint (pull_request) Successful in 3m17s
CI / Typecheck (pull_request) Successful in 3m29s
CI / Assistant Split Regression (pull_request) Successful in 3m48s
CI / Unit Tests (pull_request) Successful in 6m0s
CI / Build (pull_request) Successful in 5m31s
CI / Fresh-Linux Docker Deploy (pull_request) Failing after 4m5s
CI / E2E Tests (pull_request) Successful in 5m23s
CI / Release Images (pull_request) Has been skipped
After the Phase 3 rename the project name flipped from 'capakraken' to 'nexus'. The QNAP runner may still have capakraken-redis-1 running (holding port 6380). The down step only cleaned up the 'nexus' project, leaving the old container alive and causing "Bind for 0.0.0.0:6380 failed: port is already allocated". Add an explicit `docker compose -p capakraken ... down` before the normal cleanup so stale pre-rename containers are always removed first. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>