fix(player,studio): resolve root timeline from DOM instead of last key - #247

Ships the root-timeline resolution fix (#247), the SSR-safe player load,
and the captions import cleanup.

* fix(studio): load @hyperframes/player lazily to support SSR

Player.tsx had a bare `import "@hyperframes/player"` at module scope. The
player package registers a class that extends HTMLElement as a side effect,
and HTMLElement doesn't exist in a Node server runtime. Any consumer that
imported from @hyperframes/studio during server-side rendering (e.g. the
Next.js App Router evaluating a client component for SSR) threw
`HTMLElement is not defined`.

Move the import inside the mount effect via dynamic `import(...)` so it
only runs in the browser, and wire up a cancellation flag and deferred
cleanup so a fast unmount doesn't leak listeners or DOM nodes.

* fix(studio): remove .js extensions from captions-internal imports

The captions module imported sibling files as `./types.js` and
`./parser.js`. That's legal ESM TypeScript, but Turbopack (and other
bundlers) refuse to resolve those specifiers against .ts files when the
package is consumed from node_modules — the rest of @hyperframes/studio
uses extensionless imports for that reason.

Align captions with the rest of the codebase so the package builds
without bundler-specific configuration in consumers.

* chore: release @hyperframes/[email protected] and @hyperframes/[email protected]

Ships the root-timeline resolution fix (#247), the SSR-safe player load,
and the captions import cleanup.

Coordinated minor bump across all published packages:

- @hyperframes/cli        0.2.5 → 0.3.0
- @hyperframes/core       0.2.5 → 0.3.0
- @hyperframes/engine     0.2.5 → 0.3.0
- @hyperframes/player     0.2.7 → 0.3.0
- @hyperframes/producer   0.2.5 → 0.3.0
- @hyperframes/studio     0.2.9 → 0.3.0

Carries the two studio fixes in this PR (SSR-safe player load,
captions-internal imports) plus the DOM-based root timeline resolution
from #247.

Coordinated minor bump across all published packages.

- @hyperframes/cli        0.2.5 → 0.3.0
- @hyperframes/core       0.2.5 → 0.3.0
- @hyperframes/engine     0.2.5 → 0.3.0
- @hyperframes/player     0.2.7 → 0.3.0
- @hyperframes/producer   0.2.5 → 0.3.0
- @hyperframes/studio     0.2.9 → 0.3.0

Cuts a single versioned line under studio + player fixes that landed in
#247 and #248 (root timeline DOM resolution, SSR-safe player load, and
captions-internal import cleanup).

heygen-com#247)

Bundled previews register a master composition alongside its sub-compositions
in `window.__timelines`, e.g. { main, intro, scene2, scene5 }. Both the
player's probe and studio's getAdapter() were using `keys[keys.length - 1]`
to pick the adapter, which returned whichever timeline was registered last.

That made the player report the final sub-composition's duration as the
video length (e.g. 3.2s instead of the master's 14s) and play/pause/seek
targeted that sub-composition instead of the full composition.

Look up the outermost `[data-composition-id]` element in the iframe DOM
and use its id to select the right timeline. Falls back to last-key when
no element is present (standalone sub-composition previews) so drill-down
views keep working.

Also restores `main`/`import` entry points on @hyperframes/player to
point at compiled dist output (the src/ paths broke workspace consumers
that only receive the published tarball).

…m#248)

* fix(studio): load @hyperframes/player lazily to support SSR

Player.tsx had a bare `import "@hyperframes/player"` at module scope. The
player package registers a class that extends HTMLElement as a side effect,
and HTMLElement doesn't exist in a Node server runtime. Any consumer that
imported from @hyperframes/studio during server-side rendering (e.g. the
Next.js App Router evaluating a client component for SSR) threw
`HTMLElement is not defined`.

Move the import inside the mount effect via dynamic `import(...)` so it
only runs in the browser, and wire up a cancellation flag and deferred
cleanup so a fast unmount doesn't leak listeners or DOM nodes.

* fix(studio): remove .js extensions from captions-internal imports

The captions module imported sibling files as `./types.js` and
`./parser.js`. That's legal ESM TypeScript, but Turbopack (and other
bundlers) refuse to resolve those specifiers against .ts files when the
package is consumed from node_modules — the rest of @hyperframes/studio
uses extensionless imports for that reason.

Align captions with the rest of the codebase so the package builds
without bundler-specific configuration in consumers.

* chore: release @hyperframes/[email protected] and @hyperframes/[email protected]

Ships the root-timeline resolution fix (heygen-com#247), the SSR-safe player load,
and the captions import cleanup.