fix(core): move lottieReadiness out of src/runtime so it ships in dist

[terencecho]

Summary

The "./runtime/lottie-readiness" subpath export in @hyperframes/core claims to ship at ./dist/runtime/adapters/lottieReadiness.js, but that file is missing from the published 0.6.6 and 0.6.7 tarballs. Consumers that import the subpath — most notably @hyperframes/studio's Player.tsx — fail to resolve the module and break downstream builds (e.g. Next.js/Turbopack).

Root cause

packages/core/tsconfig.json excludes src/runtime (those files run in a browser context and are bundled separately into the IIFE artifact). Since nothing in the included tree imports lottieReadiness.ts, tsc never emits a compiled output, and the file silently goes missing from the publish.

Fix

lottieReadiness.ts is a pure helper — takes unknown, returns boolean, no DOM/window dependencies. It doesn't belong in src/runtime/ in the first place; the runtime-exclude rule rightly caught it. Move it to src/lottieReadiness.ts so the standard library build picks it up.

The subpath export name stays "./runtime/lottie-readiness" — only the exports map's underlying file path changes — so existing consumers (studio) don't need any code change.

Changes

• mv src/runtime/adapters/lottieReadiness.{ts,test.ts} -> src/
• Update src/runtime/adapters/lottie.ts re-export path
• Update package.json + publishConfig.exports to point at the new dist path (./dist/lottieReadiness.{js,d.ts})

Test plan

• pnpm typecheck (core) — clean
• bun run build (core) — dist/lottieReadiness.{js,d.ts} now present
• bunx vitest run (core) — 862/862 passing
• bun run typecheck (studio) — clean, resolves moved file via subpath export
• Publish 0.6.8 and verify the tarball contains dist/lottieReadiness.js
• Downstream consumer (e.g. hyperframes-internal/demo-next) builds without the pnpm patch workaround

🤖 Generated with Claude Code