[LeenHawk]

Add OHOS native backends for clipboard-manager, dialog, fs, notification, opener and barcode-scanner. Existing mobile plugin calls run through an Ability-scoped Rust/ArkTS bridge, with pending calls rejected on teardown and picker URI grants enforced before filesystem access.

The dialog plugin preserves OHOS browser alert/confirm instead of replacing synchronous dialogs with the initialization IIFE. Source preparation retains application version constraints and workspace inheritance, quotes Windows paths correctly, and supports application-owned runtime pins. install.py --sources-only installs derived sources/HAR/types without rewriting the application's entry/oh-package.json5, Ability or permission declarations.

Requires the native bridge in tauri-apps/tauri#16171. The default integration pins its complete Tauri/Wry/Tao/Ability baseline in shared/ohos/runtime-pins.json; consumers pass their own pins. Rust Ability and the packaged HAR come from the same checkout. Applications still directly depend on the matching napi-ohos and napi-derive-ohos crates, as documented.

Validation: rebased onto v2 at f36ba7b, preserving upstream's arboard/notify-rust upgrades and excluding its new desktop zbus dependency on OHOS. The signed submission has the same tree as the locally checked rebase. cargo check --locked passed for all six affected plugins on Linux; cargo fmt --all --check, Python syntax checks, and git diff --check passed. The diff contains no example/test changes. No new HAP/device run was performed.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[LeenHawk]

Could a maintainer review this OHOS plugin integration and consider merging it once the companion core bridge in tauri-apps/tauri#16171 is available? I have resolved the current v2 conflicts, retained upstream dependency upgrades, and pushed the GitHub-verified commit d1e62aa. All six affected plugins pass cargo check --locked on Linux, along with formatting, Python syntax and diff checks. The PR remains limited to production integration changes; no new HAP/device run is claimed. Please let me know if a different merge order or smaller split would help review. Thank you!