- Decision
- ADR-237
- Date
- 2026-11-16
- Status
- ProposedProposed (owner's choice for review B10, 2026-11-16; host-checked on the build server, not built, not on a device)
- Mentions
- ADR-215
1Decision
Amend ADR-215: an unlock made for one autofill, save or credential request (the app is not in front: LockPolicy.onUnlocked(inForeground = false)) does not start the 60 second confirmation window. An unlock with the app in front, and every confirmation in the app, still start it.
2Why and evidence
Review B10. [verified-in-source] LockPolicy.onUnlocked called onAuthenticated() for every unlock, and SessionManager passes inForeground = startedActivities > 0 for the autofill and credential paths, so a person who opened the app for one request could then show or copy a password, export or delete within a minute without a prompt although they never confirmed in the app. [measured] the new check anUnlockForOneRequestDoesNotStartTheGrace fails on the old code (a passphrase unlock for a request starts no grace) and the 12 host classes pass with the fix.
3Consequences
After an autofill unlock a first confirming action in the app asks again, once. ADR-215 otherwise stands.
4Review when
Accepted when PWM-025 passes on an image that carries it. The Passwords app is declared done (owner, 2026-11-04), so no new PWM row is run unless the owner asks.
Read from docs/governance/decision-log.md, entry ADR-237.