Two test gaps: unverified prebuild `Info.plist` and a missing `.node` fixture in the Babel plugin tests

从标记为 TODO 的测试和 packages/host/src/node/prebuilds/apple.ts 开始，包括 writeFrameworkInfoPlist，然后运行相关的单元测试。完成的标准是 prebuild 测试验证生成的 Info.plist 值，并且 Babel plugin fixture 同时包含 my-addon.js 和 my-addon.node，同时保留预期的解析结果。PR #426 已经涵盖了这项工作。

Two TODOs marking tests that assert less than they appear to.

verify-prebuilds skips the Info.plist it just found

The verifier walks each framework in the XCFramework and `continue`s past `Info.plist` without reading it. That file is written by `writeFrameworkInfoPlist` in `packages/host/src/node/prebuilds/apple.ts` from the library name and bundle identifier, and a wrong `CFBundleExecutable` or `CFBundleIdentifier` is exactly the kind of failure that passes every build step and then fails at load time on device. Parsing it and asserting the executable name matches the library, and the identifier matches what was requested, is a handful of lines given `@expo/plist` is already a dependency.

## "does not touch required JS files" doesn't prove what it claims

The test fixture has my-addon.js and asserts the plugin does not emit requireNodeAddon. But with no my-addon.node in the fixture there is nothing for the plugin to have found in the first place — the assertion passes for the wrong reason, and would keep passing even if the plugin's precedence between a .js and a sibling addon were broken. Adding a ./my-addon.node alongside it, as the TODO says, is what makes the test meaningful: with both present, require('./my-addon') must still resolve to the JS file.

Current status (as of 2026-09-23)

Both gaps above are fixed by #426, the only open PR against this issue. It's mergeable (clean), has two maintainer approvals (2026-08-16 and 2026-08-28), and CI is fully green on the current head commit (Lint + Unit tests on ubuntu/macos/windows; native app/device jobs skipped, which is expected for a fork PR without runner secrets/labels). Nothing about the PR has changed since the second approval on 2026-08-28 — it's been sitting approved, mergeable and green for over three weeks. Nothing further is needed here besides merging it — no competing implementation work is warranted.

Earlier independent attempts (#448, #449, #450, #455) were closed in favor of #426 once it became clear it already covered the same fixes (the shared isNodeApiModule .js/.node precedence bug, plus zod-validated Info.plist verification).