Repository navigation
Conversation
R4 account-scope integration boundaryThis source remains Keep backup consent/ownership reviews independent. Per-account opt-in/legacy migration/readback/registration repair and pending A -> B backup/label/key operations still need actual native/staged acceptance. Reconcile the combined setup correction during source integration; do not drop the guard to make onboarding work. Current combined tests 380 Jest / 308 recovery pass; source approval and final own-head/native checks remain open. No backup/key mutation on the owner's device, merge or release occurred. |
Scope
Exact-head verification
Current head:
81bc417cb.node --test tests/recovery/*.test.cjspasses 261/261. Regression fixtures cover A→B before execution, during connectivity, before queued transport, while Realm still has A open, and before/after vault registration repair upload.git diff --checkpasses. TypeScript diagnostics compared with the #7038 base remain 1,399 baseline error lines versus 1,388 here, with zero new diagnostic messages; the repository-wide typecheck still has existing failures. All fixtures are disposable. No real account, key, backup, consent, production database, or credential was used.Baseline integration rehearsal
This draft is stacked on #7038, which is stacked on #7027. #7031 is a separate, open
sprintbaseline PR and is not an ancestor. An isolated, unpushed merge rehearsal of #7031 with this R4 stack resolved six source/test conflicts, kept #7031's persistence-failure and cancellation behavior, and passed 273/273 recovery tests plus 19/19 release tests at local rehearsal headf10cb6ddc. The rehearsal is evidence for the merge path, not a change to the PR branches.Review and release gates
sprint; its prior approval was dismissed. R4: Make read-only backup verification resilient to sync and network races #7027 and these two R4 drafts also require developer review. Resolve the rehearsed conflicts and rerun CI on the eventual release head.7040; rerun when that service is healthy.