v2.0.3

fix: name Auto Blocker instead of sending the user to check Wi-Fi

The toggle failed with "무선 디버깅을 켤 수 없습니다. Wi-Fi 연결을 확인한 뒤
다시 시도해 주세요" on a phone whose Wi-Fi was fine. It was always going to
say something untrue there: the engine checks Wi-Fi at the top of the same
method and gives up if it is missing, so reaching that line proves Wi-Fi is
connected. The message contradicted what the code already knew, and cost
someone an afternoon looking in the wrong place.

What actually stops it, on a Galaxy, is 보안 위험 자동 차단 - Auto Blocker.
While it is on, wireless debugging cannot be enabled by anything, this app
included. It was invisible during development because it had been switched
off to allow sideloading in the first place.

That failure has its own type now, so the screen can put up a dialog with a
way to the setting rather than a toast telling the user to go and find it.
There is no documented action that opens Auto Blocker directly, so it opens
the security settings screen and the dialog says which row - a guessed
Samsung component name would resolve to nothing on the builds it guessed
wrong for.

The setup screen carries the same line under its steps. Auto Blocker stops a
first-time user at step 2, silently: the switch just refuses to stay on,
with nothing on screen to explain it, and the app looks broken.

Also fixed in the harness: the notification checks reported zero on a run
where the service had simply never started. It polled for the notification
but never asked for the service again, and start-foreground-service gets
dropped often enough on a loaded emulator that waiting was never going to
help. It reissues the start while it waits.

Android 16: 9 checks, no failures. 57 unit tests.