EISDIR regression (0.5.3→0.5.7) + navigation timeout on complex compositions (macOS M4)

[sarichan777]

Describe the bug

1. EISDIR regression between v0.5.3 and v0.5.7

All versions from 0.5.7 onward fail immediately at 0% with EISDIR: illegal operation on a directory, read on any composition. Version 0.5.3 compiles and starts frame capture successfully.

Version	Compiles?	Frame capture?
0.5.0	yes	yes
0.5.3	yes	yes
0.5.7	no (EISDIR)	--
0.6.0	no (EISDIR)	--
0.6.71	no (EISDIR)	--
0.6.72	no (EISDIR)	--

2. Navigation timeout on complex compositions

On v0.5.3, a real 930-second composition (6 videos, 35 fonts, 250+ asset files) compiles successfully but times out on frame capture: Navigation timeout of 60000 ms exceeded.

Request: a --browser-timeout CLI flag or env var to increase the navigation timeout.

Link to reproduction

https://github.com/sarichan777/hyperframes-repro (minimal reproduction: single layer, no external assets, no GSAP)

Steps to reproduce

1. Create a minimal composition with a single layer, no external assets, no GSAP
2. Run npx hyperframes@0.5.3 render --composition . → compiles and starts frame capture ✓
3. Run npx hyperframes@0.6.72 render --composition . → EISDIR: illegal operation on a directory, read at 0% ✗
4. For the timeout: use a real composition with 6 videos, 35 fonts, 250+ assets
5. Run npx hyperframes@0.5.3 render --composition . → compiles but Navigation timeout of 60000 ms exceeded at 25%

Expected behavior

1. Any version from 0.5.7+ should compile and render a minimal composition without EISDIR errors, same as 0.5.3 does.
2. Complex compositions should allow a configurable navigation timeout (or auto-scale it) rather than hard-failing at 60 seconds.

Actual behavior

1. EISDIR: All versions 0.5.7+ fail immediately at 0% with EISDIR: illegal operation on a directory, read regardless of composition complexity or Docker mode. The error occurs before the compile stage.
2. Timeout: Version 0.5.3 compiles the full composition but the browser hits a hard 60-second page navigation timeout before frame capture can start.

Environment

Version          0.6.72 (latest)
Node.js          v22
OS               macOS 26.5 (Darwin arm64)
Architecture     arm64 (M4 Max, 128 GB)
Docker           Docker Desktop

Additional context

No response

[jrusso1020]

@sarichan777 should go out in the next release