Hartmut/Nexus
1
0
Fork 0
Code Issues 11 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

rename(phase 1): CapaKraken → Nexus across code, UI, docs, CI (#61)
CI / Architecture Guardrails (push) Successful in 2m38s
Details
CI / Assistant Split Regression (push) Successful in 3m33s
Details
CI / Typecheck (push) Successful in 3m51s
Details
CI / Lint (push) Successful in 5m2s
Details
CI / E2E Tests (push) Has been cancelled
Details
CI / Fresh-Linux Docker Deploy (push) Has been cancelled
Details
CI / Release Images (push) Has been cancelled
Details
CI / Build (push) Has been cancelled
Details
CI / Unit Tests (push) Has been cancelled
Details

Browse Source 
rename(phase 1): CapaKraken → Nexus across code, UI, docs, CI (#61)

Co-authored-by: Hartmut Nörenberg <hn@hartmut-noerenberg.com>
Co-committed-by: Hartmut Nörenberg <hn@hartmut-noerenberg.com>
This commit was merged in pull request #61.
This commit is contained in:
Hartmut Nörenberg
2026-05-21 16:28:40 +02:00
committed by Hartmut
parent d9a7ec0338
commit b41c1d2501
943 changed files with 24548 additions and 16832 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/demand-assignment-migration-cutover.md
+7 -6
View File
@@ -24,9 +24,9 @@ pnpm db:readiness:demand-assignment --write-artifacts
Supporting commands:
```bash
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 --filter @nexus/db db:audit:demand-assignment --json --fail-on-blockers
pnpm --filter @nexus/db db:backfill:demand-assignment --json --fail-on-blockers
pnpm --filter @nexus/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 @capakraken/db db:backfill:demand-assignment --apply`
- run `pnpm --filter @nexus/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 @capakraken/db db:backfill:demand-assignment --apply --json` was executed on `2026-03-13` and completed as a no-op:
The first real `pnpm --filter @nexus/db db:backfill:demand-assignment --apply --json` was executed on `2026-03-13` and completed as a no-op:
- `demandCreates: 0`
- `assignmentCreates: 0`
@@ -177,6 +177,7 @@ As of `2026-03-14`, the split persistence migration is fully complete through St
### Facade Retirement (Complete)
The former compatibility facades have been renamed to clean domain names:
- `update-allocation-with-compatibility` → `update-allocation-entry`
- `delete-allocation-facade-entry` → `delete-allocation-entry`
- `fill-open-demand-with-compatibility` → `fill-open-demand`
@@ -184,7 +185,7 @@ The former compatibility facades have been renamed to clean domain names:
All `AllocationFacade*` type prefixes have been replaced with `AllocationEntry*`. All `compatibilityId` and `source` fields have been removed from booking interfaces. Variable names like `demandRequirementByCompatibilityId` and `existingFacade` have been renamed to `demandRequirementById` and `resolved`. Test descriptions referencing "compatibility" have been updated.
No legacy *compatibility* naming (e.g. `compatibilityId`, `AllocationFacade*`, `WithCompatibility`, `FillPlaceholder`) remains in the codebase. The `isPlaceholder` property and `"placeholder"` strategy values are intentionally retained as derived read-model contracts — they describe the demand-vs-assignment distinction at the frontend consumption layer, not legacy migration artifacts.
No legacy _compatibility_ naming (e.g. `compatibilityId`, `AllocationFacade*`, `WithCompatibility`, `FillPlaceholder`) remains in the codebase. The `isPlaceholder` property and `"placeholder"` strategy values are intentionally retained as derived read-model contracts — they describe the demand-vs-assignment distinction at the frontend consumption layer, not legacy migration artifacts.
## Parallel Workstream Note