Bundle, build and run iOS test app in separate steps in production + ccache enabled

[kraenhansen]

Supersedes #360, which forked from main at 80ae73b and became unmergeable when the workspace migrated from npm to pnpm — package-lock.json was deleted on main and modified there, so GitHub could not compute a merge ref and CI had nothing to run against.

This is #360 rebased onto current main, plus three fixes to the iOS job. Getting some inspiration from prior art.

Rebased from #360

The six commits are faithful ports; the only change inside them is npm ci / npx → pnpm install / pnpm exec, forced by the pnpm migration.

• Bundle, build and run the iOS test app as separate steps rather than through test:ios:allTests, so a build failure is distinguishable from a test failure.
• Enable ccache for the Xcode build. The Xcode project injects its own CCACHE_CONFIGPATH, so the config written by hendrikmuhs/ccache-action doesn't propagate — CCACHE_DIR / CCACHE_MAXSIZE / CCACHE_COMPILERCHECK are re-exported through $GITHUB_ENV, where they take precedence.
• Drop the JDK and Android SDK setup from the iOS job.
• Add x86_64-apple-ios as a default ferric target on Apple hosts. This is Rust's x86_64 iOS simulator target, so without it ferric produced an arm64-only slice while CMAKE_RN_TRIPLETS: arm64;x86_64-apple-ios-sim produced a fat one, and linking failed on the mismatch.
• Print the module path when framework slicing fails, which is what surfaced that mismatch.
• Ad-hoc signing, and archive for generic/platform=iOS Simulator.

One commit from #360 is dropped: 623c875 "Dedupe and update package lock (and upgrade prettier)". It was a package-lock.json rewrite, and that file no longer exists. What survived it — the @prettier/plugin-oxc 0.0.4 → 0.1.3 bump and the reformat it caused in copy-examples.mts — would desync package.json from the committed pnpm-lock.yaml and break pnpm install --frozen-lockfile. That upgrade is worth doing separately, with a regenerated lockfile.

Additional fixes

Isolated in three commits on top, so any can be dropped independently.

• Bundle before pod install. react-native-test-app resolves the resources declared in app.json when it generates the workspace (validate_resources in ios/test_app.rb), warning about and skipping any that don't exist yet: "CocoaPods will not include resources it cannot find […] make sure they exist, then run pod install again." Bundling afterwards left dist/main.ios.jsbundle out of the app, so it expected a Metro dev server that CI never starts. Also --assets-dest dist rather than dist/res — dist/res is the Android convention, whereas React Native's iOS bundler writes into <assets-dest>/assets and app.json declares dist/assets for iOS.
• Pick an available iPhone simulator instead of hard-coding iPhone 17, wait for it with simctl bootstatus -b, and address it by UDID rather than the booted alias. macos-latest rolls forward and the device lineup changes with each Xcode release.
• shell: bash on the xcodebuild step. A bare run: is bash -e {0} without pipefail, so xcodebuild … | xcbeautify reported xcbeautify's exit code and a failing build was swallowed.

Testing

Verified locally: pnpm install --frozen-lockfile, pnpm run build and pnpm run prettier:check pass.

Two things could not be verified in the Linux container this was prepared in, and are for CI to confirm:

• pnpm run lint reports 4 no-unsafe-* errors in apps/test-app/App.tsx, which need the weak-node-api / ferric-example bootstrap that the Lint job runs.
• pnpm test fails 4 path-utils permission tests, which are root-user artifacts (chmod 000 doesn't stop root). These come from main and pass on CI.

The iOS build and simulator run are not reproducible without an Apple toolchain, so the three fixes above are reasoned from react-native-test-app's source and GitHub's shell semantics rather than observed green. This PR needs the Apple 🍎 label for the Test app (iOS) job to run.

---

Generated by Claude Code