What step 9 did cover before the two blocked calls: a web client of this tip, signed in on a fresh key and invited into the same chat, was reacted to from the desktop and drew the chip on its own message — so the selection, the scope rule and the delivery are exercised on the web too. What was not observed is the browser drawing the notification and the words it carries.
The gate at this tip: `:app-core:jvmTest :ui:jvmTest` plus both app compiles; the wasm suites of app-core, ui and app-web; `:app-web:e2e` 48 + 152 checks. `NotificationReplyTest.aReplyGoesOutWithNoSessionOpenAndNoStreams` timed out once in three rounds of `:app-core:jvmTest` and passed in the other two — unrelated to this diff (it reaches no code here) and worth a flake issue of its own.