What

• add a Camera Hub Commands sample MOD for protocol 1 tts.speak and panTilt.move
• execute speech through the active context.audio.say() provider
• convert dashboard pan/tilt degrees into context.motion.setPose() body poses
• validate command envelopes and payload bounds, preserve body position and roll, and return protocol-compatible acknowledgements
• keep all Camera Hub protocol handling out of the host runtime and public host capabilities
• add focused Moddable tests and Japanese integration documentation

Architecture

Camera Hub command interpretation is application-specific and now lives entirely under firmware/mods/examples/camera_hub_commands.

A future generic moddable-tailscale wrapper may live under the host context.connectivity namespace and own Tailnet startup, MagicDNS, WebSocket transport, reconnect, and lifecycle. The MOD will consume that transport and remain responsible for JSON command semantics and mapping commands to Stack-chan audio/motion capabilities.

This PR does not add the Tailnet transport yet. The current MOD exposes executeCameraHubCommand() as the protocol boundary and does not connect to the hub by itself.

Impact

Release impact: minor for the new sample MOD. Existing host capabilities and runtime composition are unchanged.

Changeset: .changeset/private-camera-hub-commands.md.

Checks

• npm run format -- --write mods/examples/camera_hub_commands: passes
• npm run lint -- mods/examples/camera_hub_commands: passes with one pre-existing informational finding outside this MOD
• npm run check:architecture: 74 passed
• Node behavior smoke for speech, movement, malformed input, and unsupported commands: passed
• npm run mod:build -- m5stackchan_cores3 ./mods/examples/camera_hub_commands/manifest.json: passed
• GitHub Actions: both Moddable test shards, Linux host and mini-app smoke tests, fast tests, web visual tests, bundle, and every release target passed

The first Linux smoke attempt did not reach the host-ready marker and had no exception log. Re-running the same job without code changes passed both smoke targets, confirming a transient mcsim startup failure.