The prepare step was exiting with code 0 but never generating diffs
or writing manifest.json. Added step-by-step logging to diagnose:
- 'Generating ppk diff...' / 'Ppk diff generated.'
- 'Generating package diff...' / 'Package diff generated.'
- 'Manifest written to ...'
- 'prepare-local-update-artifacts completed successfully.'

Inlined diff calls (removed generatePpkDiff/generateAndroidPackageDiff
wrapper functions) for more direct error propagation.

The in-process require of lib/diff.js + calling diffCommands.hdiff()
was hanging because yauzl's async entry callbacks don't keep the
Node.js event loop alive properly when called from a script that
has no other active handles.

Switched to running diff commands as CLI subprocesses via runPushy(),
matching the pattern already used for bundleTo(). Each diff command
runs in its own node process with a proper event loop.

Also removed the DiffCommandRunner type and lib/diff.js require since
they're no longer needed.

The CLI's loadModule('node-hdiffpatch') searches from process.cwd(),
which is the project root when running as a subprocess. Install the
module to the project's node_modules instead of the CLI's so it can
be found.

This ensures pushy hdiff/hdiffFromApk commands can resolve the native
diff module when run as CLI subprocesses.

macOS 26 runner requires explicit tap trust for Homebrew security.
Fixes: Refusing to load formula wix/brew/applesimutils from untrusted tap

The local e2e server appears to start (health check passes) but returns
404 for artifact files. Added:
- stdout/stderr capture from bun server subprocess
- spawn error handler
- HTTP response status logging in waitForRequestReady

Root cause was CLI's loadModule not checking NODE_PATH dirs.
Fixed in react-native-update-cli@151ea0f.

- prepare script: verify ppk.patch and apk.patch exist after generation
- server: log 404 responses with resolved path and existence check
- server: add /debug/artifacts endpoint listing all files
- globalSetup: capture server stdout/stderr to .server.log
- globalSetup: list artifacts dir and query debug endpoint before warmServer

Root cause: loadModule('node-hdiffpatch') in CLI's lib/diff.js uses
require.resolve with paths=['.', ...NODE_PATH]. The '.' resolves to
cliRoot/lib/, and NODE_PATH only had cliRoot/node_modules/. But
node-hdiffpatch was installed in projectRoot/node_modules/, which was
not in the search path. The module silently failed to load, the diff
command exited without error (or with a swallowed error), and the
output file was never created.

Fix: add projectRoot/node_modules to NODE_PATH so the CLI can find
node-hdiffpatch installed in the project's node_modules.

pushy hdiff exits 0 but doesn't create the output file. Capture and
log all stdout/stderr from the CLI subprocess to understand why.

…rectly

pushy hdiff exits 0 in CI but doesn't create output files. The root
cause is that the CLI's bin.ts flow (loadSession, argument parsing)
interferes with the hdiff command somehow - the handler either never
runs or silently fails.

Fix: use a standalone wrapper script (run-hdiff-wrapper.js) that
requires the CLI's lib/diff module directly and calls the hdiff/hdiffFromApk
handlers with the correct arguments. This bypasses the bin.ts flow
entirely while reusing the same diff logic.

Also adds projectRoot/node_modules to NODE_PATH so the CLI's
loadModule can find node-hdiffpatch installed in the project.

- Use createRequire from node:module for reliable module loading
- Add extensive logging to diagnose wrapper execution in CI
- Validate input files exist before calling diff handlers
- Verify output file creation after diff completes

__dirname in TS-compiled scripts points to .e2e-artifacts/.ts-build/scripts/,
but run-hdiff-wrapper.js lives in the source scripts/ directory and is not
copied to the build output. Use projectRoot + 'scripts' to resolve correctly.

The CLI's loadModule uses require.resolve with paths that only include
the CLI's own lib/ and node_modules/. It cannot find node-hdiffpatch
installed in the project's node_modules.

Fix: pre-load node-hdiffpatch from project root in the wrapper script
and pass it as options.customHdiffModule to the diff handler. This
bypasses the loadModule resolution entirely.