Phase 4 cleanup: drop legacy capakraken DB + role after stability window #63
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
The CapaKraken → Nexus rename completed on 2026-05-21. The cutover script:
capakrakenDB to/tmp/capakraken-pre-rename-20260521-201019.sqlnexusDB+role and restored all data into itnexuscompose project nameThe old
capakrakenDB and role were intentionally retained for the rollback window.When to action
After 2026-05-28 (7 days of stable operation on
nexus) — verify the app is healthy, then proceed.Checklist
nexusfor ≥7 days (logins work, MFA works, no data loss)apps/web/src/app/layout.tsx(~30 lines of inline<script>that copiescapakraken_*keys tonexus_*on first load). Open a PR with labelcleanup/rename-shim.Notes
/tmp/capakraken-pre-rename-20260521-201019.sql— keep until this issue is closedcapakrakenstring in code (DEFAULT_ANONYMIZATION_SEEDinpackages/api/src/lib/anonymization.ts) must not be changed — it is a cryptographic constant; changing it would invalidate all stored anonymization aliases