Diagnostic-only release on top of v1.0-build47. Single Swift change.
Fixes a long-standing diagnostic gap: captcha-view events from the
WebView coordinator were silently dropped during pre-bootstrap
captcha (when the extension hasn't started yet) because they were
only routed through sendProviderMessage to the extension. Now they
also write directly to the App Group vpn.log from the main-app
process, so events are always visible regardless of extension state.
Motivated by github issue #5 follow-up (DaRk1c3, blank captcha on
build 47): the user-supplied log showed "showing WebView" followed
by "user dismissed captcha — aborting" 13.6 seconds later with ZERO
intermediate [captcha-view] events. That absence wasn't evidence
that the WebView didn't render — it was evidence that we couldn't
see what it did. With this fix, the next reproduction will show
either:
- WebView rendered fine (Nav, Loaded, JS state events fire) → bug
is in user perception or VK-side rendering - WebView started navigating but failed (didFailProvisionalNavigation
fires) → likely VPN routing or TLS issue - WebView never navigated → SwiftUI sheet binding or URL parse issue
Cost: one extra log line per event during mid-session captcha (when
both diagnostic paths reach the file in parallel). Acceptable for
diagnostic visibility. WRAP layer, active-probe gate, and all other
build 47 behaviour unchanged.