match gets eaten by previous unfinished match call

To reproduce:
- Lock the screen
- Unlock by typing the password
- Lock the screen
- Try to unlock with fingerprint. The first time you touch the sensor nothing will happen. Then the 2nd time you touch the sensor the match will actually unlock the screen or show "no match"

Workaround:
- Just keep touching the sensor until something happens (shouldn't have to do it >5 times)
- Always try to unlock with fingerprint and only try unlocking with password if you run out of attempts

Start by reproducing the lock, password unlock, relock, and fingerprint sequence described in the issue. No file, test, or entry point is named, so trace the fingerprint match call lifecycle and identify why the first post-password sensor attempt is ignored. Done means the first fingerprint attempt produces the expected unlock or no-match result.

Written by the indexing model from the issue text.