0.4.4

Android foreground verification now accepts a complete WindowManager window-type token at the end of a line. Multiline attributes previously caused foreground_window_type_missing and blocked valid app observations and actions.

The fix retains the OS owner, UID, Activity, process lifetime, window lifetime and action-target checks. It applies to ordinary Android windows as well as clone hosts; window titles remain display data rather than proof of app ownership.

All public Bridge components are aligned to 0.4.4: CLI/MCP, Android SDK and Gradle plugin, six Android executors, iOS Swift SDK, Flutter SDK and optional test helper, and Web SDK. Internal native store remains 0.2.0. SDK execution behavior is unchanged.

Validation: 109 foreground/action regressions; 1,402 Host functional tests and 50 serial performance tests; Android build/lint and 194 debug + 194 release SDK tests, 8 plugin tests and 47 UIA tests; unsigned iPhoneOS build; Flutter analysis and 66 SDK tests; Web 23 tests. Final CLI archive installation, MCP, extraction, Script, Runtime and native prebuild checks are verified separately.

The same parser source was validated on a physical device with Dida clone Home and two tab actions leading to login. This is not full account or whole-app acceptance. Shark bookkeeping initialization remains a separate Duo investigation.