Android foreground checks previously interpreted a client window title as package ownership. A host-owned window with a guest package in its title could therefore be rejected even when the caller supplied the intended allowlist.

0.4.3 resolves the focused WindowState's actual owner and Activity, verifies PackageManager UID and process lifetime, and compares that identity through observation and action dispatch. Ordinary Activity windows, app dialogs and explicitly identified non-Activity windows retain their package and UIA guards. Unlisted apps, replaced windows and restarted processes require a new observation or remain rejected.

All public components use 0.4.3: CLI/MCP, Android SDK, Gradle plugin and six executors, iOS Swift package, Flutter SDK/test helper and Web SDK. The internal native store remains 0.2.0.

Validation includes Host functional/performance suites, native package installation with compilers denied, Android builds/lint/JVM tests, Swift iPhoneOS build, Flutter analysis/66 tests, and Web 23 tests. A real Android 36 emulator reproduced the old failure in an ordinary app with a projected title, then passed the packaged CLI/MCP's observation, counter action, dialog and rejection scenarios. API36/37 owner queries also passed on existing devices. API25/30 dump formats were checked against AOSP and tested offline; those versions were not available for live validation in this release.

AI App Bridge 0.4.2 adds an independent emergency reset for stuck Android tasks. A lost terminal callback, an abandoned agent, or a blocked Host queue no longer requires the original task to finish before device occupancy can be reset.

ai-app-bridge device-ownership --operation force-stop --serial SERIAL --extract null

MCP: run device-ownership with {operation:"force-stop",serial:"SERIAL"} and extract:null. Occupancy errors and unresolved status include a short recovery hint with these arguments.

The control runs in the CLI/MCP client before Runtime connection or version checks. It terminates the recorded owner and shared Host, stops the selected phone's UIA and managed shell workers and recorded SDK/test apps, archives original task history, and clears occupancy. Other tasks in those Host processes also stop. Already dispatched effects are not rolled back; abandoned outcomes remain force_stopped/unknown.

If the phone is disconnected, local occupancy is released and remoteResetPending:true identifies the remaining phone reset. Reconnect and repeat the command. The reset remains available after a reset-client crash, corrupt task record, or PID reuse.

All public components use 0.4.2: CLI/MCP and Web npm packages, Android SDK/plugin and six test executors on JitPack, iOS Swift Package, Flutter SDK and test helper on pub.dev. The internal native store remains 0.2.0.

Validation: 1388 Host tests, 47 UIA JVM tests, 66 Flutter SDK tests and 23 Web tests passed. Android build/lint/unit tests and iPhoneOS Swift build passed; both Flutter publish prechecks reported zero warnings. The Flutter helper has no test directory. The final CLI tarball passed fresh installation and CLI/MCP checks. On b46093e6, the original unresolved operation was reset, a running UIA executor was forcibly stopped, and a new MCP session observed and operated the device, ending at idle/active=0.

Upgrade with npm install -g @mobileaidev/ai-app-bridge@0.4.2. Reconnect existing MCP clients to load the new client-side control. This release does not constitute business acceptance of any consumer app.

All Bridge components are released together as 0.4.1: CLI/MCP, Android SDK/Gradle plugin/executors, iOS Swift package, Flutter SDK/helper, and Web SDK.

• Fix iOS observation controls leaving unresolved device-action ownership. Explicit ios-execution reconcile can retire the exact observation marker left by older Hosts, while unknown UI actions still require their original completion proof.
• Preserve successful extraction values and original extraction errors when temporary-directory cleanup fails; report cleanup separately as extraction.cleanupError.
• SDK runtime identities, dependencies, installation examples and package versions are aligned. Device/Web execution behavior and the 0.4.0 extraction/budget contract are unchanged.

Install the Host with npm install -g @mobileaidev/ai-app-bridge@0.4.1, then reconnect MCP clients. Node >=26.3.0 <27 is required. Upgrade an older shared Runtime explicitly after its tasks finish; installation does not reload existing processes.

Validation: 1,378 Host tests, three installed-package regression probes, clean tarball installation and MCP/CLI checks, Android SDK/plugin/executor build and lint, iOS SDK build, 66 Flutter SDK tests, 23 Web tests, and actual iPhone ownership recovery/continued launch with the existing SDK 0.4.0 app. Flutter helper analysis and publication validation passed; it has no test directory. Device SDK changes in this patch are version/dependency alignment, without a new app installation or business-flow acceptance claim.

AI App Bridge 0.4.0 makes response size and extraction explicit across CLI and MCP. It includes regex, JavaScript and Python extraction, bounded response delivery, retained response reads, improved Script diagnostics and four native prebuild targets.

Migration

• External run calls now require extract. Pass null for the complete response within the output budget; CLI callers use --extract null.
• Read command execution and control facts from the public envelope. Extraction failure does not replay the command; use the saved source ref to retry extraction.
• Default compact JSON response budget: 96 KiB. Replace old _history / _meta handling with the public control fields.
• Node >=26.3.0 <27 is required. Ordinary MCP, JavaScript and regex need neither Python nor a compiler; Python is needed only for Python execution. FactStore is bundled, with no separate service to install.
• Restart existing MCP connections after upgrading. Existing processes do not reload when npm installs a new package.

Validation

1375 Host tests, 138 NotallyX fixture tests, 66 Flutter tests and 23 Web tests passed. Android SDK/plugin/executors and Swift packages built successfully. Four macOS/Linux native targets passed clean-install and CLI/MCP checks. OPPO test-app and iPhone Kiwix SDK 0.4.0 flows passed. Actual Codex and Cursor clients preserved the required nullable/oneOf schema and executed null, regex, JavaScript and Python requests.

Native targets cover macOS arm64/x64 and Linux glibc arm64/x64. Windows and musl are not supported in this release. Minimum macOS/glibc versions and physical x64 hardware were not exercised; x64 checks used Rosetta. Device checks are scoped to Bridge integration, not complete consumer business acceptance.

Detailed acceptance: M4 record.

Published packages

• CLI/MCP on npm
• Web SDK on npm
• Flutter SDK on pub.dev
• Flutter test helper on pub.dev

JitPack successfully built the tagged commit; all 16 public POM/binary files for the Android SDK, Gradle plugin and six executor modules were verified. npm latest and next both point to 0.4.0. Public npm archives match the accepted tarballs byte for byte; pub.dev archive hashes and source contents were verified.

AI App Bridge 0.3.8 adds executor-prepare for preparing optional UI executors in existing projects, through CLI, MCP, JavaScript, and Python.

• Android generates the androidTest session entry and injects test dependencies for one build, preserving the application ID and business source. Espresso, UI Automator, Espresso-Web, and Compose remain explicit choices.
• Flutter adds the exact test helper as a dev dependency, generates the entry under build, checks production dependency versions, and restores dependency files on conflicts or partial Pub failures.
• iOS reuses a verified WDA/XCTest source cache. Web prepares pinned Playwright and browser dependencies outside the page SDK.
• Espresso adds explicit Unicode input through InputConnection, alongside the existing setter and key input choices. Standard androidTest APKs without version attributes are accepted with package/signature/hash verification.

Validation: 1338 CLI tests, 66 Flutter SDK tests, 23 Web SDK tests, Android builds, and root Swift Package iOS build passed. On OPPO, NotallyX's JS/Python regressions each completed 70 steps and 18 assertions in about 27 seconds, followed by independent SQLite verification. LocalSend's JS/Python flows and iPhone XCTest/H5 flows also passed. Real Chromium checks covered forms, dialogs, Shadow DOM, cross-origin iframes, upload, popups, and navigation identity.

Automatic preparation uses the existing platform toolchain; npm does not install Android SDK/JDK, Flutter, Xcode, or Python. Flutter WidgetTester launch currently supports Android; Flutter iOS continues through the existing SDK/WDA path. The executed flows are documented coverage, not a claim that every feature of every App was tested.

Integration and compatibility · Repeatable NotallyX scripts

Android Host 前台窗口解析修复

修复多条焦点记录中 null 排在有效窗口前时误报 foreground_not_found 的问题：读取全部记录并跳过空值；单个有效窗口直接使用，多个窗口按系统当前焦点屏幕选择，仍不能唯一定位时明确返回 foreground_ambiguous。

包名匹配、窗口和控件有效性检查保留。行为修改仅涉及 Host，各 SDK 和辅助包统一同步为 0.3.7。

验证

• 新增 15 项解析与派发保护测试；相关测试 85 项、完整 CLI 检查 1328 项通过。
• K2 Mini（API 25）和 YIC-R68P（API 30）的点按、输入及启动核验通过；使用设备已有 SDK 0.3.6 即可验证 Host 修复。
• Android 全模块构建、Flutter 66 项测试、Web 23 项测试和根 Swift Package 的 iOS Simulator 编译通过。
• 公开 npm/pub 归档完整性及 JitPack 0.3.7 产物校验通过；同批接入项目依赖已更新并完成对应构建。

升级

npm install -g @mobileaidev/ai-app-bridge@0.3.7

Web：@mobileaidev/ai-app-bridge-web@0.3.7。Flutter：ai_app_bridge_flutter: 0.3.7；可选测试辅助包 ai_app_bridge_test: 0.3.7。Android SDK/Gradle 插件使用 JitPack 0.3.7；原生 iOS 使用 Git tag 0.3.7。

升级 Host 后核对 CLI/MCP 的版本和共享 Runtime 身份。消费 App 的依赖更新与构建不表示已安装到设备或完成全部业务验收。

发布、项目更新和验证记录

AI App Bridge 0.3.6 disables continuous UI observation by default across Android, iOS, Flutter, Web and embedded H5. Observation is explicitly bounded to 100–5000 ms and expires locally; Flutter snapshots are read on demand. Update the CLI/MCP and App SDK together.

This release also adds optional Android Instrumentation/UI Automator/Espresso/WebView/Compose adapters, a Flutter integration_test helper, and Playwright execution. JavaScript and Python scripts use the shared command and execution contracts. Testing dependencies remain opt-in.

Validation includes 1313 CLI checks, a clean installation of the actual npm tarball with 121 public commands, Android release builds and lint, a clean root Swift Package iOS build, Flutter and Web checks, and real Android/iPhone UI-observation lifecycle and performance probes. Device probes do not establish full business acceptance for consumer apps.

Artifacts: npm CLI/Web 0.3.6, pub ai_app_bridge_flutter and ai_app_bridge_test 0.3.6, Swift Package tag 0.3.6, and JitPack Android SDK/plugin plus six optional test adapters.

See release and upgrade instructions and UI observation measurements.

0.3.5 修复 Android UIA 回执启动审计、旧版 Android UIA/权限观察，以及 iOS 隧道探测和失败启动的所有权对账。Host、CLI、MCP、Runtime 与 SDK 版本统一为 0.3.5。

• UIA journal 从原始绑定 ref 读取 nodeRef；保留原 session 证据，经公开 start 审计后创建新 runtime，不删除锁文件。
• UIA node runtime 支持 API 25+，保留 POSIX 锁、原子重命名和 fsync。OnePlus/API 36 与 K2 Mini/API 25 的回调计数、stop/start、进程死亡恢复及旧引用拒绝均有真机证据。收银机/API 30 完成只读 UIA 观察。
• iOS 对未就绪的 list 快照进行选定设备 details 探测；原 CoreDevice 4016 failed JSON 与 XCTest 初始化失败可通过公开接口精确对账，身份不匹配仍拒绝。
• 空闲设备上取消未知安装返回 install_action_not_pending，不再暗示成功取消。
• 更新 Python 断言、freeze/thaw、Script result 与证据完整性文档；Kiwix 重启后明确打开书签列表，NotallyX 示例控制器使用当前 Script API。

渠道已核验：npm CLI/Web 的 latest 与 next 均为 0.3.5，pub.dev 的 Flutter 0.3.5 已发布，JitPack 的 SDK/AAR 和 Gradle 插件/JAR 均对应本 tag。Swift package 使用 tag 0.3.5。

验证包含实际 npm tarball 的干净安装与 CLI/MCP 共享 Runtime、Android/Swift 构建、Web 单测与 Chrome 控件契约，以及选定真机业务。新增 WDA 的 24 项针对性测试通过；Host 全套低并发运行 1298/1299 通过，唯一性能阈值项原样单独运行通过，未放宽阈值。

本次发布不声明 115 条能力全部完成跨平台独立业务验收。具体业务结果与未覆盖范围见仓库 docs/RELEASE_HANDOFF_0.3.5_2026-09-14.md；原始设备证据和未通过的尝试分别保留。

CLI and MCP now share the same Runtime when automatic ADB discovery, an explicit path, or a symlink resolves to the same executable. Runtime startup pins the resolved path; genuinely different ADB selections still require an explicit stop. A missing ADB does not block capabilities that do not use Android.

This coordinated release carries version 0.3.4 across CLI/MCP, Android SDK and Gradle plugin, iOS Swift package, Flutter, and Web. Device SDK behavior is unchanged from 0.3.3; all 0.3.3 fixes remain included.

Validation: 1,287 CLI tests passed, including the original CLI/MCP configuration failure and bidirectional Script result recovery. The exact npm tarball passed a clean install and shared Runtime checks. Android release/plugin and iOS native sample builds passed; Flutter publication dry-run reported zero warnings. This does not claim a new full cross-platform App regression.

Repairs foreground observations after navigation, Android SHA-256 compatibility on devices that expose only BusyBox/Toybox, and iOS failed-launch ownership recovery. Adds explicit cancellation of a retained original Android installation session, without retrying the installation or claiming rollback.

CLI --version, recording directory handling, Script authoring examples and field errors are corrected. Android, iOS, Flutter, Web and CLI/MCP use coordinated version 0.3.3.

Validation: 1,284 CLI tests plus 49 final installation/contract checks; Android Debug/Release 185 tests each, Gradle plugin 6 and UIA 43; Web 22; root Swift Package iOS build; clean npm tarball installation and CLI/MCP protocol checks. Targeted device evidence covers K2 Android 7.1, Reader navigation on OPPO, iOS launch rejection/recovery and controlled original-session cancellation. This is not a claim of complete cross-platform business regression.

Install with npm @mobileaidev/ai-app-bridge@0.3.3, npm @mobileaidev/ai-app-bridge-web@0.3.3, pub.dev ai_app_bridge_flutter: 0.3.3, or the matching JitPack/SPM tag. Reconnect existing MCP clients after upgrade.

CLI/MCP now exposes a light command directory and lets agents request only the operation they need. Intent decisions can be narrowed by platform, provider and action. All 115 commands and the complete contracts remain available.

The packaged ai-app-bridge-use skill keeps the target, observation, action receipt and persisted-result contracts, with detailed documentation loaded on demand. Duplicate schema unions are flattened without changing the execution contracts.

All consumer versions are aligned to 0.3.2: CLI/MCP, Android SDK and Gradle plugin, native iOS Git tag, Flutter on pub.dev, and the Web npm package. Android/iOS/Flutter/Web execution behavior is unchanged in this patch.

Validation includes a fresh npm tarball installation with native compilation and CLI/MCP protocol checks, public Android JitPack artifacts, Flutter publication checks, and a Reader real-device reading workflow. The root SPM iOS Simulator build passed on the 0.3.1 source; the 0.3.2 native iOS source changes only the SDK version marker.

Reader Intent observations were turned into a Script. With both the globally installed CLI/MCP and the installed Reader Android SDK at 0.3.2, the final run completed 46 calls and 23 device assertions in 23.337 seconds, with no failed or inconclusive assertions. Reading, chapter selection, settings and reopening the book were verified. Mobile events and the final result were persisted; the evidence archive passed integrity verification and includes four screenshots. This validates the selected reading workflow; full-app regression remains outside this release check.

The failed 0.3.1 JitPack build record remains available. A fresh 0.3.2 build succeeded with the original performance thresholds and runtime implementation unchanged.

AI App Bridge 0.3.0 makes the verified rc.3 implementation the default release across CLI/MCP, Android, iOS, Flutter, and Web. The repository main branch and installation guides now use this version. SDK-reported version fields and fixed dependencies are aligned; execution behavior is unchanged from rc.3.

Default installation:

npm install -g @mobileaidev/ai-app-bridge
npm install @mobileaidev/ai-app-bridge-web
flutter pub add ai_app_bridge_flutter

• npm latest and next both point to 0.3.0.
• Android SDK: com.github.mobileAiDev.ai-app-bridge:ai-app-bridge-android:0.3.0 from JitPack.
• Android Gradle plugin: com.github.mobileAiDev.ai-app-bridge:ai-app-bridge-gradle-plugin:0.3.0; plugin ID io.github.mobileaidev.aiappbridge.android.
• Flutter: ai_app_bridge_flutter: ^0.3.0 from pub.dev.
• Native iOS: repository-root Swift package, Git tag 0.3.0, product AiAppBridgeIOS.

The release includes the shared CLI/MCP Runtime, Intent and JavaScript/Python Script execution, durable Script final-result retrieval, explicit native/H5 target binding, persistent evidence queries, and refreshed command and skill documentation. Android retains API 19 support through explicit local-server-socket cleanup when the accept loop exits.

The CLI requires Node >=26.3.0 <27 and native build tools. Script clients read final results using script operation=result; Flutter H5 adapters provide isVisible and explicit target binding. See the release and integration guide.

Existing real-app results and the remaining business acceptance matrix are recorded separately from the release channel. The latest Wikipedia script, combined four-app run, and remaining iOS/cross-device scenarios remain in the fixed acceptance handoff.

AI App Bridge 0.3.0-rc.3 coordinates the CLI/MCP, Android SDK and Gradle plugin, Flutter plugin, Web SDK, and native iOS Swift package.

Intent and Script share an independent Runtime across CLI and MCP. This candidate includes durable Script final-result retrieval, explicit Flutter/H5 target binding, aligned Intent action permissions, packaged native storage, and updated command/skill documentation.

The rc.3 change preserves Android API 19 support by explicitly closing the local server socket after its accept loop exits, avoiding an API 28-only Closeable conversion. It also retains the rc.2 correction of an obsolete Android stress-test expectation for the in-memory capture view and aligns candidate versions and installation examples. Memory-only results remain unavailable and uncommitted; all capacity and heap-growth checks remain enforced. The CLI execution code and bundled SDK files are identical to the verified rc.1 package.

Install the candidate explicitly:

npm install -g @mobileaidev/ai-app-bridge@0.3.0-rc.3
npm install @mobileaidev/ai-app-bridge-web@0.3.0-rc.3

• npm candidates use next; latest remains the previous stable release.
• Android SDK: com.github.mobileAiDev.ai-app-bridge:ai-app-bridge-android:0.3.0-rc.3 from JitPack.
• Android Gradle plugin module: com.github.mobileAiDev.ai-app-bridge:ai-app-bridge-gradle-plugin:0.3.0-rc.3; plugin ID io.github.mobileaidev.aiappbridge.android.
• Flutter: ai_app_bridge_flutter: 0.3.0-rc.3 from pub.dev.
• Native iOS: repository-root Swift package, exact Git tag 0.3.0-rc.3, product AiAppBridgeIOS.
• The native store is bundled with the CLI; no separate npm publication is required. Flutter's local podspec does not require a CocoaPods trunk release.

The CLI requires Node >=26.3.0 <27 and native build tools. Migrate final-result readers to script operation=result; Flutter H5 adapters must provide isVisible and explicit target binding. See the release guide.

This is a release candidate. Existing real-app evidence covers the principal Intent/Script workflows; the full business acceptance matrix remains incomplete, including the latest Wikipedia script, the combined four-app run, and remaining iOS/cross-device scenarios. See the engineering handoff.

• Adds Flutter iOS plugin publication support with vendored AiAppBridgeIOS runtime sources.
• Declares the iOS Flutter plugin platform and starts the Swift runtime in the debug app process.

• Uses the JitPack Android runtime 0.2.8 coordinate for debug builds.

• Uses Android runtime 0.2.8 for debug builds.

Update Android runtime docs to 0.2.1

Migrate package coordinates to mobileAiDev

• Uses Android runtime 0.1.9 for debug builds, including the native Unicode-safe /v1/action/input-text bridge endpoint.

Add bridge-native Unicode text input

Harden network and installer capture

Add WebView CDP capture

Release bridge runtime and CLI hardening

• Automatically includes the Android debug runtime from the Flutter plugin's Android debug variant.
• Lowers the Android runtime minimum SDK to 21.
• Broadens the package SDK constraint to Dart 3.0+ / Flutter 3.10+.
• Documents that Flutter apps should call WidgetsFlutterBinding.ensureInitialized() before bridge initialization.

• Aligns the Flutter package version with the Android bridge and desktop CLI 0.1.4 release.
• Updates package metadata for the public 0.1.4 release.