feat(js): merge host package into reachy-mini-sdk

[tfrere]

Summary

Fold @pollen-robotics/reachy-mini-host into @pollen-robotics/reachy-mini-sdk so app authors install, version, and import from a single entry point. The SDK and the host shell already shipped in lockstep (single repo, single release); the second package was just extra friction.

- "@pollen-robotics/reachy-mini-host": "^1.x",
- "@pollen-robotics/reachy-mini-sdk":  "^1.x"
+ "@pollen-robotics/reachy-mini-sdk":  "^1.x"

- import { mountHost }        from '@pollen-robotics/reachy-mini-host/auto';
- import { connectToHost }    from '@pollen-robotics/reachy-mini-host/embed';
- import { PROTOCOL_VERSION } from '@pollen-robotics/reachy-mini-host/protocol';
+ import { mountHost }        from '@pollen-robotics/reachy-mini-sdk/host/auto';
+ import { connectToHost }    from '@pollen-robotics/reachy-mini-sdk/host/embed';
+ import { PROTOCOL_VERSION } from '@pollen-robotics/reachy-mini-sdk/host/protocol';

What changes

Layout

• js/host/ → js/sdk/host/ (the whole directory; git tracks it as a pure rename so blame survives)
• js/sdk/host/src/lib/sdk-types.ts → js/sdk/reachy-mini-sdk.d.ts (the canonical type declarations now ship as the .d.ts companion next to the SDK runtime; host re-exports them from the new location)
• js/package.json (workspace root) deleted: there is now a single npm package, js/sdk/
• js/package-lock.json → js/sdk/package-lock.json

Package surface (js/sdk/package.json)

Single package, new subpath exports:

Export	Resolves to	Use
.	reachy-mini-sdk.js	The ReachyMini class (unchanged)
./host	host/dist/index.js	mountHost, connectToHost, types
./host/auto	host/dist/entry/auto.js	CDN auto bundle
./host/embed	host/dist/entry/embed.js	CDN embed bundle
./host/protocol	host/dist/lib/protocol.js	PROTOCOL_VERSION, helpers

React/MUI/Emotion deps + devDeps for the host build moved into the SDK package. npm run build (from js/sdk/) drives vite + tsc end-to-end.

Runtime cleanup

The host's entry/auto.ts, entry/embed.ts and the ./host npm entry now import ReachyMini directly from the SDK module and self-assign window.ReachyMini (when unset) before exposing window.ReachyMiniHost / window.ReachyMiniHostEmbed. Effects:

• Apps consuming the host no longer need a separate <script type="module"> to load the SDK on the global.
• Legacy apps that still set window.ReachyMini themselves are untouched (we only assign when missing).
• useSdk / connectToHost stop racing against a late-arriving global.

Log-prefix tag harmonised to [reachy-mini-sdk/host] / [reachy-mini-sdk/host/embed] for greppability.

CI

.github/workflows/npm-publish.yml simplified: one npm ci, one npm run build, one npm publish (no more --workspace=sdk / --workspace=host pairs). The version-from-pyproject.toml flow is unchanged.

Docs

• js/README.md rewritten for the single-package layout (with a migration note).
• js/sdk/README.md adds the ./host subpath section + migration note.
• js/sdk/host/{README,SPEC,APP_AUTHOR_GUIDE,CHANGELOG}.md updated to the new import paths.
• docs/source/SDK/javascript-sdk.md cross-links the host subpath exports.

Compat / rollout

• @pollen-robotics/reachy-mini-host stays available on npm at its current version for one minor cycle so consumers can switch on their own schedule, then we'll npm deprecate it with a pointer to the new subpaths. The post-deprecation tarball is a tiny shim that re-exports from @pollen-robotics/reachy-mini-sdk/host.
• Reference apps (reachy_mini_emotions, reachy_mini_telepresence, reachy_mini_minimal_conversation) are already on ^1.7.3 of both packages and have been independently migrated to the new import paths (see the corresponding app repos).

Test plan

• cd js/sdk && npm ci && npm run typecheck && npm run build (clean)
• cd js/sdk && npm pack --dry-run — single tarball, contains reachy-mini-sdk.js, reachy-mini-sdk.d.ts, host/dist/, host/{README,SPEC,APP_AUTHOR_GUIDE,CHANGELOG}.md
• CI dry-run on the PR (npm-publish workflow re-pointed at js/sdk/)
• Manual smoke: load host/dist/entry/auto.js from a local Space — host renders, window.ReachyMini is set without an SDK script tag
• Manual smoke: import mountHost from @pollen-robotics/reachy-mini-sdk/host in a bundler-driven app, confirm SDK is initialised before useSdk reads it

Made with Cursor

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.