General: Record the interrupted-session device verification

[d4rken]

What changed

No user-facing behavior change — documentation only. The qualification ledger now records that interrupted-session detection was verified on real hardware, and a stale known-gap entry is removed.

Technical Context

• Ledger — the Pixel row's coverage gains "interrupted-session detection (7a)". The 2026-07-25 run on the Pixel 7a (lynx, A16/API36, WSS-granted) exercised the whole path: a force-stop mid-session left charge_optimization_mode=0 while the app was dead, the next open restored it to 1 and surfaced the card (USER_STOPPED / RESTORED_LATE), Dismiss cleared both card and stored keys, a force-stop without a session recorded nothing, and a real reboot restored via boot recovery with no card — the boot-count guard doing its job. dumpsys activity exit-info confirmed the classifier matched the owning PID's exit (reason 10, subreason FORCE_STOP).
• Known gaps — the "recovery notification lingers until swiped" entry is gone because it is fixed: the notification is now cancelled on a later successful restore, on recovery convergence, and on an explicit policy write.
• Protocol — step 4 now names both interruption expectations, plus the practical detail that cost time on the device: a phone holding at its limit reports NOT_CHARGING, which ends a session the moment it starts, so the lifecycle has to be driven with dumpsys battery set status/level and reset afterwards.