[tiensonqin]

Summary

Fix two failures found by real iOS Simulator native input: SwiftUI propagates an editor identifier to auxiliary non-editor elements, and focusing an editor introduces keyboard/text-service windows.

• Resolve standard editors by explicit identifier and native editor type, for both frame publication and actions. Count every eligible editor before enabled/hittable validation; equivalent duplicate controls still reject. Other kinds retain all-types uniqueness.
• Select exactly one content window using public XCTest containing predicates anchored by explicit LUI identifiers. Keep foreground and probe-viewport checks; do not select a window by index, private class or hittability.
• Document the migration: even settle/screenshots require an explicit identifier on real LUI content. Unanchored trees and multiple independent scenes remain unsupported. No wire change or semantic fallback.

Validation

• One fresh, isolated XCTest on a real iOS 26.5 Simulator, using the actual Drive native TCP CLI and the LUI backend/read-only probe fixture: increment, Unicode and empty replacement, focus/keys, settle, screenshot and disabled-target rejection passed.
• Apple build-for-testing and existing Drive checks passed in the macOS session. The committed runner is the exact source used in the successful native run.
• No retained fixture or test changes.

Limits

This is backend/probe/XCTest integration evidence, not OCaml application-core integration. Duplicate-editor and multiple-content-window negative cases, other editor kinds, drag/scroll and physical devices were not exercised. Windows without the snapshot's explicit identifiers cannot be recognized as independent content.

Native evidence

Link to Devin session: https://app.devin.ai/sessions/9bf68438070747fb8b5c0c6718836a56
Open in Devin Desktop: https://app.devin.ai/desktop/session/9bf68438070747fb8b5c0c6718836a56?variant=devin
Requested by: @tiensonqin

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring