robotics-connect → split into per-robot MHS connectors

This repository has been split. robotics-connect was a monorepo bundling several robots, a shared core, and simulation tooling. It is now decomposed into focused, per-robot repos under the arm-mhs-<vendor>-<robot> naming convention, each registered as a connector in the MHS registry. This repo is kept as an umbrella / landing page (history, links, and cross-cutting issues live on here); new work happens in the repos below.

The repos

Repo	What it is	MHS registry connector
arm-mhs-robotkit	Robot-agnostic shared core: locomotion / navigation / safe-stop / task-gate ABCs, the ROS2 twist binding, the MHS driver sidecar, and vendor-neutral robot skills. Every connector below depends on it.	— (library)
arm-mhs-unitree-g1	Unitree G1 EDU humanoid connector + on-robot control stack.	arm-mhs-unitree-g1
arm-mhs-unitree-go2	Unitree Go2 quadruped + D1 servo-arm connector + stack.	arm-mhs-unitree-go2
arm-mhs-human-partner	A human partner (Bluetooth headset) mounted as an MHS device, so a robot can ask a person for help over the fabric.	arm-mhs-human-partner
arm-mhs-nvidia-isaaclab	Peripheral NVIDIA Isaac Sim + Isaac Lab RL/sim tooling: sim staging, RL env, sensor staging, DGX Spark bring-up, policy deploy.	— (tooling)

Connector maintainers vs. hardware vendors

Each registry entry carries a maintainers key distinguishing the hardware vendor (e.g. Unitree Robotics) from the connector maintainer (Arm). The connectors are built on the MHS driver model (MhsDriver, @rpc/@emit), retargeted from Arm Device Connect.

What stayed here

This umbrella still hosts the cross-cutting issues that span more than one of the new repos (framework positioning, packaging/hardening, and the multi-repo cleanup batches). See the open issues. Safety guidance lives in SAFETY.md; the pre-split source tree remains in this repo's history and on the main branch for reference.