feat(session): add database preparation boundary PR 1 - #5158
Open
MohamadJaara wants to merge 1 commit into
Open
Conversation
This was referenced Aug 11, 2026
MohamadJaara
marked this pull request as ready for review
August 11, 2026 16:27
saleniuk
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
Add the Android boundary for Kalium's explicit user-session database preparation lifecycle.
Changes
Impact
This is a foundation-only change. It introduces no screen or consumer behavior yet; later PRs use this boundary before accessing a user database.
Stack
mo/epic/async-db-migration