[PM-39035] Document client lock states#818
Conversation
🤖 Bitwarden Claude Code ReviewOverall Assessment: REQUEST CHANGES Reviewed the new Code Review Details
|
Deploying contributing-docs with
|
| Latest commit: |
6eeb1ff
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d8fd63f9.contributing-docs.pages.dev |
| Branch Preview URL: | https://km-lock-states.contributing-docs.pages.dev |
…cs into km/lock-states
withinfocus
left a comment
There was a problem hiding this comment.
Significant but clean documentation improvements. You can wait on someone from your team to also give the nod on a deeper technical review but this works for me.
Thomas-Avery
left a comment
There was a problem hiding this comment.
Looks good some minor things from me.
Co-authored-by: Thomas Avery <43214426+Thomas-Avery@users.noreply.github.com>
Co-authored-by: Thomas Avery <43214426+Thomas-Avery@users.noreply.github.com>
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-39035
📔 Objective
Add a deep-dive page documenting the lock states a Bitwarden client moves through: logged out, locked before-first-unlock (BFU), locked after-first-unlock (AFU), and unlocked. Explains that some secrets are held in memory only and re-hydrated on unlock, so feature behavior differs by state.
📸 Screenshots
n/a (docs only)