Motion, MotionHandle, and ServoSession

Target motion includes move_to(), move_joint(), move_finger() / flex_finger(), and move_thumb(). Parameters can include duration, speed, gains, and time step as allowed by each versioned signature.

MotionHandle provides bounded waiting, cancellation, state, and error access. A returned handle does not imply completion.

open_servo() creates an application-driven ServoSession. send_position(), send_velocity(), send_current(), send_impedance(), and send_mit() all accept complete hand frames whose array lengths equal the active layout's joint count. The SDK does not provide joint-, finger-, or thumb-only streaming methods that implicitly retain other targets. start_servo_drag() is SDK-managed drag control and must not overlap with another owner of motion control.

Teaching records trajectories; replay sends them back after the application verifies layout compatibility and range. See the motion guide for operation and recovery rules.