feat(migration): complete Step 1 of ActiveDid migration - update () to use new API
- Update () to call () with fallback to settings
- Maintain backward compatibility while using new active_identity table
- Update migration plan documentation to reflect completed Step 1
- Restore Playwright workers to 4 (was accidentally set to 1)
Tests: 39/40 passing (1 unrelated UI failure)
Migration progress: Step 1 complete, ready for Step 2 dual-write implementation
@ -31,10 +31,10 @@ Follow this implementation checklist step-by-step to complete the migration.
### Phase 2: API Layer Updates ❌ INCOMPLETE
### Phase 2: API Layer Updates ❌ INCOMPLETE
- [x] Implement `$getActiveIdentity()` method (exists but wrong return type)
- [x] Implement `$getActiveIdentity()` method (exists but wrong return type)
- [x] Fix `$getActiveIdentity()` return type to match documented interface
- [x] Fix `$getActiveIdentity()` return type to match documented interface
- [] Update `$accountSettings()` to use new method
- [x] Update `$accountSettings()` to use new method
- [ ] Update `$updateActiveDid()` with dual-write pattern
- [ ] Update `$updateActiveDid()` with dual-write pattern
**Status**: Return type fixed. Method now returns `{ activeDid: string }` as documented. Need to update other API methods.
**Status**: $accountSettings() now uses new API. Method combines settings with activeDid from active_identity table. Need to implement dual-write pattern.
### Phase 3: Component Updates ❌ BLOCKED
### Phase 3: Component Updates ❌ BLOCKED
- [ ] Update 35+ components to use `$getActiveIdentity()`
- [ ] Update 35+ components to use `$getActiveIdentity()`