chore: full technical rename planarchy → capakraken

Complete rename of all technical identifiers across the codebase:

Package names (11 packages):
- @planarchy/* → @capakraken/* in all package.json, tsconfig, imports

Import statements: 277 files, 548 occurrences replaced

Database & Docker:
- PostgreSQL user/db: planarchy → capakraken
- Docker volumes: planarchy_pgdata → capakraken_pgdata
- Connection strings updated in docker-compose, .env, CI

CI/CD:
- GitHub Actions workflow: all filter commands updated
- Test database credentials updated

Infrastructure:
- Redis channel: planarchy:sse → capakraken:sse
- Logger service name: planarchy-api → capakraken-api
- Anonymization seed updated
- Start/stop/restart scripts updated

Test data:
- Seed emails: @planarchy.dev → @capakraken.dev
- E2E test credentials: all 11 spec files updated
- Email defaults: @planarchy.app → @capakraken.app
- localStorage keys: planarchy_* → capakraken_*

Documentation: 30+ .md files updated

Verification:
- pnpm install: workspace resolution works
- TypeScript: only pre-existing TS2589 (no new errors)
- Engine: 310/310 tests pass
- Staffing: 37/37 tests pass

Co-Authored-By: claude-flow <ruv@ruv.net>

docs/demand-assignment-migration-cutover.md

@@ -24,9 +24,9 @@ pnpm db:readiness:demand-assignment --write-artifacts
 Supporting commands:
 
 ```bash
-pnpm --filter @planarchy/db db:audit:demand-assignment --json --fail-on-blockers
-pnpm --filter @planarchy/db db:backfill:demand-assignment --json --fail-on-blockers
-pnpm --filter @planarchy/db db:backfill:demand-assignment --apply
+pnpm --filter @capakraken/db db:audit:demand-assignment --json --fail-on-blockers
+pnpm --filter @capakraken/db db:backfill:demand-assignment --json --fail-on-blockers
+pnpm --filter @capakraken/db db:backfill:demand-assignment --apply
 ```
 
 `pnpm db:readiness:demand-assignment` fails with a non-zero exit code when the workspace is not ready for `--apply`. Use `--allow-blockers` only when collecting review artifacts before remediation.
@@ -86,7 +86,7 @@ No production backfill should run from an ad hoc shell session without the saved
 
 ### Stage 3: Apply Backfill
 
-- run `pnpm --filter @planarchy/db db:backfill:demand-assignment --apply`
+- run `pnpm --filter @capakraken/db db:backfill:demand-assignment --apply`
 - immediately rerun `pnpm db:readiness:demand-assignment --write-artifacts`
 - require the post-apply readiness report to remain `go`
 
@@ -129,7 +129,7 @@ The latest workspace readiness run on `2026-03-13T20:10:43.050Z` reported:
 - dry-run creates: `0` demand, `0` assignment
 - `goNoGo: "go"`
 
-The first real `pnpm --filter @planarchy/db db:backfill:demand-assignment --apply --json` was executed on `2026-03-13` and completed as a no-op:
+The first real `pnpm --filter @capakraken/db db:backfill:demand-assignment --apply --json` was executed on `2026-03-13` and completed as a no-op:
 
 - `demandCreates: 0`
 - `assignmentCreates: 0`