@pollen-robotics/reachy-mini-sdk 1.7.3-main.5cd69ad

package/CHANGELOG.md

@@ -0,0 +1,188 @@
+# Changelog
+
+All notable changes to `@pollen-robotics/reachy-mini-sdk` are
+documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Versions
+are kept in lock-step with the Reachy Mini Python daemon and are
+driven from `pyproject.toml` at the repo root (the npm publish CI
+overrides the `version` placeholder in `package.json`).
+
+The host shell shares this package's version (single source of
+truth); the wire protocol is versioned separately in
+`PROTOCOL_VERSION` (see [host/SPEC.md §11](./host/SPEC.md#11-backlog)).
+
+## Unreleased — succeeds 1.7.3
+
+> **Breaking change.** Every app currently using
+> `@pollen-robotics/reachy-mini-host` has to update its imports
+> when it upgrades. Existing `1.7.x` installs keep working against
+> the legacy `reachy-mini-host@1.7.x` tarball that stays on npm;
+> only consumers who upgrade past `1.7.3` need to migrate. The
+> target version is intentionally left unset in this PR — it will
+> be picked at release time when `pyproject.toml` is bumped from
+> `1.7.3` to the next number (the npm publish CI mirrors that bump
+> into the package manifest).
+
+**Single-package release: `@pollen-robotics/reachy-mini-host` is folded
+into `@pollen-robotics/reachy-mini-sdk`.** App authors install,
+version, and import from one entry point. The old package stays
+available on npm at `1.7.x` for one minor cycle for graceful
+migration and will then be `npm deprecate`d with a pointer to the
+new subpaths.
+
+### Migration
+
+```diff
+- "@pollen-robotics/reachy-mini-host": "^1.7.x",
+- "@pollen-robotics/reachy-mini-sdk":  "^1.7.x"
++ "@pollen-robotics/reachy-mini-sdk":  "^<next-release>"
+```
+
+```diff
+- 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';
+```
+
+The host CDN bundles also moved:
+
+```diff
+- https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-host@1/dist/entry/auto.js
++ https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/auto.js
+```
+
+### Added
+
+- New subpath exports on `@pollen-robotics/reachy-mini-sdk`:
+  - `./host`           — `mountHost`, `connectToHost`, types
+  - `./host/auto`      — CDN auto bundle for standalone apps
+  - `./host/embed`     — CDN embed bundle for the iframe side
+  - `./host/protocol`  — `PROTOCOL_VERSION`, `decodeCredsFromHash`, etc.
+- `reachy-mini-sdk.d.ts` ships next to `reachy-mini-sdk.js` as the
+  canonical SDK type surface. The host re-exports from there
+  (`host/src/lib/sdk-types.ts` is now a thin barrel), removing the
+  earlier duplication TODO.
+
+### Changed
+
+- The host bundles (`./host`, `./host/auto`, `./host/embed`) now
+  import the SDK runtime directly and self-assign
+  `window.ReachyMini` (when unset) at module-load time, dispatching
+  `reachymini:ready`. App `index.html` files no longer need a
+  separate `<script type="module">` to load the SDK on the global,
+  and `useSdk` + `connectToHost` no longer race against a
+  late-arriving global. Apps that still set `window.ReachyMini`
+  themselves are unaffected — we only assign when it's missing.
+- Log-prefix tag harmonised to `[reachy-mini-sdk/host]` /
+  `[reachy-mini-sdk/host/embed]` for greppability.
+- Internal repo layout: `js/sdk/*` collapsed into `js/*` now that
+  there is only one package. The host source lives at `js/host/`,
+  the SDK runtime at `js/reachy-mini-sdk.js`, the package manifest
+  at `js/package.json`. No effect on consumers; only the
+  `repository.directory` field and the npm-publish CI working
+  directory changed.
+
+### Removed
+
+- Workspace coordinator `js/package.json` (was an npm workspace
+  root) and `js/package-lock.json` at the workspace level. The
+  single package's lockfile lives at `js/package-lock.json`.
+- `@pollen-robotics/reachy-mini-host` package manifest — the host
+  ships under `@pollen-robotics/reachy-mini-sdk/host*` now. The
+  legacy npm package stays on `1.7.x` for one minor cycle for
+  graceful migration, then will be `npm deprecate`d.
+
+### SDK changes drafted between 1.7.3 and the package merge
+
+The following landed on `main` after `1.7.3` was published but
+were never released on their own; they ship with this release:
+
+- **Breaking (SDK)**: `wakeUp()` and `gotoSleep()` now return
+  `Promise<void>` (previously `boolean`). The promise resolves on
+  the daemon's `{command, completed: true}` response, after the
+  trajectory player has fully landed. Apps that previously relied
+  on the boolean return are unaffected in practice; apps that
+  *want* to await trajectory completion (e.g. to chain
+  `setMotorMode("disabled")` after a `gotoSleep`) can now do so
+  without racing.
+- **SDK**: both motion helpers take an optional `{ timeoutMs }`
+  (default 8000 ms). The promise rejects on session teardown
+  (`stopSession` / `disconnect`) so consumers never wait forever
+  on an interrupted trajectory.
+- **SDK**: `POST /send` responses with a 4xx / 5xx status now
+  produce a `console.warn` carrying the rejected message `type`
+  and the response body, making racy `setPeerStatus` /
+  `endSession` failures easier to diagnose.
+- **Host types**: `src/lib/sdk-types.ts` refreshed to cover the
+  full SDK public surface (`autoConnect`, `gotoTarget`,
+  `setMotorTorque`, `subscribeLogs`, `requestState`, version /
+  hardware-id helpers, `robotState`, `isEmbedded`, jitter buffer
+  option, `autoStartFromUrl`). The motion helpers now type as
+  `Promise<void>` to match the SDK.
+
+## 0.3.0 - 2026-05-16 (unreleased)
+
+**This release is a full rewrite of the package against
+[SPEC.md v1.0](./host/SPEC.md).** The public surface and the wire
+protocol both change in incompatible ways.
+
+### Breaking changes
+
+- **API**: `mountHost()` options reduced to the documented surface
+  (`appName`, `appIconUrl`, `appEmoji`, `enableMicrophone`,
+  `clientId`, `devToken`, `target`). The following are removed:
+  - `theme: { light, dark }` (host owns its bundled MUI theme).
+  - `skipTheme` (no consumer-driven theming).
+  - `skipAuth` (host owns OAuth).
+- **API**: `ConnectedHandle` reduced to the documented surface.
+  The following are removed:
+  - `sendCustom()` / `onCustom()` (no free-form bidi channel).
+  - `requestConfigUpdate()` (apps don't push config upstream).
+- **API**: `devToken` payload renamed `{ token, username }` →
+  `{ token, userName }` for camelCase consistency with `appName`
+  and `hostName`.
+- **API**: `ConnectedHandle.username` renamed to `ConnectedHandle.userName`.
+- **Protocol**: `host:custom` / `embed:custom` removed.
+- **Protocol**: `embed:request-config-update` removed.
+- **Host shell**: removed the legacy `?app=<owner>/<space>`
+  branding-swap behaviour. The host renders exactly the app it
+  ships with, never another. Multi-app routing now lives in the
+  mobile catalog only.
+
+### Added
+
+- `SPEC.md` (v1.0): behavioural contract, state machines,
+  4 engineering invariants (single SDK per tab, token hygiene,
+  bundle pinning, React Strict Mode safety).
+- `APP_AUTHOR_GUIDE.md`: step-by-step guide for building a new
+  app on top of the host.
+- `REBUILD_PLAN.md`: project plan tracking the rewrite (deleted
+  once 0.3.0 ships).
+- `LICENSE` (MIT).
+
+### Changed
+
+- **Documentation**: replaced the legacy `SPEC.md` (823 lines,
+  ambitious-future spec) with a focused v1.0 spec (~620 lines)
+  matching what we actually want to ship.
+- **Package metadata**: `repository.url` now points at the
+  host-only repo. `homepage` and `bugs` added.
+- **Versioning policy**: stays permissive pre-1.0 (see SPEC §11
+  "Versioning policy"); each minor release between 0.x.y may
+  ship breaking changes. Semver-strict starts at 1.0.
+
+### Why a rewrite instead of a refactor
+
+See `REBUILD_PLAN.md` § "Why a rebuild, not a refactor". TL;DR:
+the API surface shrinks too much, and the previous code carried
+half-implemented features (protocol-version negotiation,
+heartbeat, custom channels) that were cheaper to retype than to
+selectively remove.
+
+## 0.2.0 - 2026-05-15
+
+Initial extraction of the host shell into a standalone package.
+Predates the SPEC.md v1.0 rewrite; deprecated in favour of 0.3.0.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 Pollen Robotics
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,129 @@
+# @pollen-robotics/reachy-mini-sdk
+
+The JS package for [Reachy Mini](https://github.com/pollen-robotics/reachy_mini). It ships:
+
+- The **browser SDK** (`ReachyMini` class) for direct WebRTC control — the default export.
+- An optional **host shell** (OAuth + robot picker + iframe bridge) for apps deployed as Hugging Face Spaces, exposed under the `./host*` subpaths.
+
+Both used to be separate npm packages (`@pollen-robotics/reachy-mini-sdk` + `@pollen-robotics/reachy-mini-host`); they were merged into a single entry point so app authors only install, version, and import from one place.
+
+The full SDK API reference lives in the JSDoc header of [`reachy-mini-sdk.js`](./reachy-mini-sdk.js): constructor options, read-only properties, the `disconnected → connected → streaming` state machine, the event list, and every command helper.
+
+## Install
+
+### With a bundler / Node
+
+```bash
+npm install @pollen-robotics/reachy-mini-sdk
+```
+
+```js
+// Low-level robot control
+import { ReachyMini } from "@pollen-robotics/reachy-mini-sdk";
+
+// Host shell for Hugging Face Spaces apps (OAuth + picker + iframe)
+import { mountHost } from "@pollen-robotics/reachy-mini-sdk/host";
+import { connectToHost } from "@pollen-robotics/reachy-mini-sdk/host/embed";
+import { PROTOCOL_VERSION } from "@pollen-robotics/reachy-mini-sdk/host/protocol";
+```
+
+### From a browser, no build step (Hugging Face Spaces, static hosting…)
+
+Use an ESM CDN. The `+esm` suffix tells jsdelivr to resolve bare specifiers (the `@huggingface/hub` dependency) recursively, so the import just works:
+
+```js
+import { ReachyMini } from "https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/+esm";
+```
+
+Or via esm.sh:
+
+```js
+import { ReachyMini } from "https://esm.sh/@pollen-robotics/reachy-mini-sdk@1";
+```
+
+Track bleeding-edge from `main`:
+
+```js
+import { ReachyMini } from "https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@main/+esm";
+```
+
+The host CDN bundles live under the same package:
+
+```html
+<!-- Standalone host shell entry -->
+<script type="module"
+  src="https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/auto.js">
+</script>
+
+<!-- Embed-side client (inside the iframe) -->
+<script type="module"
+  src="https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/embed.js">
+</script>
+```
+
+Both bundles auto-install the SDK on `window.ReachyMini` at load time, so an app that uses the host no longer needs a separate `<script type="module">` to expose the SDK.
+
+## Quick start (SDK only)
+
+```js
+import { ReachyMini } from "@pollen-robotics/reachy-mini-sdk";
+
+const robot = new ReachyMini();
+
+// 1. Auth (HuggingFace OAuth — required by the signaling server)
+if (!await robot.authenticate()) { robot.login(); return; }
+
+// 2. Connect to the signaling server
+await robot.connect();
+
+// 3. Pick a robot once the list arrives
+robot.addEventListener("robotsChanged", (e) => {
+    const robots = e.detail.robots;  // [{ id, meta: { name } }, ...]
+});
+
+// 4. Start a WebRTC session
+const detach = robot.attachVideo(document.querySelector("video"));
+await robot.startSession(robotId);
+
+// 5. Send commands — degree-friendly helpers
+robot.setHeadRpyDeg(0, 10, -5);
+robot.setAntennasDeg(30, -30);
+robot.setBodyYawDeg(15);
+robot.playSound("wake_up.wav");
+```
+
+See the JSDoc header in [`reachy-mini-sdk.js`](./reachy-mini-sdk.js) for the full surface (events, raw `setTarget`, audio controls, embedded-mode auto-start, etc.).
+
+## Host shell
+
+For Hugging Face Spaces apps that need OAuth + a robot picker + iframe lifecycle management:
+
+- [`host/README.md`](./host/README.md) — quickstart and integration overview
+- [`host/APP_AUTHOR_GUIDE.md`](./host/APP_AUTHOR_GUIDE.md) — full guide for app authors
+- [`host/SPEC.md`](./host/SPEC.md) — host ↔ embed protocol spec
+
+## Migration from `@pollen-robotics/reachy-mini-host`
+
+```diff
+- 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';
+```
+
+You can drop `@pollen-robotics/reachy-mini-host` from your `package.json`. The host CDN bundles also moved — adjust the jsdelivr URL in your `index.html`:
+
+```diff
+- https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-host@1/dist/entry/auto.js
++ https://cdn.jsdelivr.net/npm/@pollen-robotics/reachy-mini-sdk@1/host/dist/entry/auto.js
+```
+
+The host bundles now import the SDK directly and assign it on `window.ReachyMini` at load time, so apps no longer need a second `<script type="module">` for the SDK alone.
+
+See the [CHANGELOG](./CHANGELOG.md) for the full release history.
+
+## License
+
+Apache-2.0 — see [LICENSE](./LICENSE).