[TomCC7]

Contribution path

• PRD: Manipulation SDK preview, discussion #3923.
• Stacked on fix(openyam): align learning stack with canonical model #3853.

Problem

• LeRobot's dependency environment conflicts with the host stack.
• Policy chunks need explicit execution, validation, preemption, and cancellation through the coordinator.

Solution

• Run LeRobot in an isolated Python project behind the host LeRobotPolicyModule contract.
• Own generic rollout behavior here: checkpoint/live-input preflight, ordered action chunks, freshness checks, and explicit start/stop.
• Add named trajectory execution/cancellation, joint-limit validation, accepted-command telemetry, and idle-hold support to the control layer.
• Keep cancellation ordered after in-flight submissions and report uncertain cancellation.
• Publish debounced Quest button edges while retaining continuous grip/trigger inputs.
• Keep robot-specific rollout composition in feat(imitation): add controlled OpenYAM policy rollout #3855; collection consumes accepted-command telemetry in feat(imitation): add native OpenYAM collection #3854.

API shape

LeRobotPolicyModule
  inputs: color_image: Image, coordinator_joint_state: JointState
          button_pressed: Buttons (optional operator input)
  config: policy_path, task, device, joint_names, fps,
          image_width, image_height, max_observation_age_s,
          trajectory_task_name, rollout_button
  control: PolicyControlSpec → execute_trajectory / cancel_trajectory

• RolloutControlSpec: preflight_rollout(), start_rollout(), stop_rollout(), rollout_status().
• Preflight loads/validates the checkpoint and current inputs without sending motion.
• This is the existing single-camera LeRobot contract, not a generalized backend/remapping API.

How to Test

Exercise the isolated runtime contract without robot hardware:

cd dimos/imitation/policy/lerobot/python
uv run --isolated --locked --group tests --with-editable ../../../../../ python -m pytest

• At this layer, 398 affected host tests and 27 isolated-runtime tests passed In the previous cleanup. The final stack also passed 413 control/Quest regression tests and all 36 isolated policy/preparation tests.

• Scoped type checks and commit hooks passed.

• Physical rollout and cancellation remain hardware release checks; mock tests are not safety certification.

• The repository-wide Clippy hook reaches an existing dim_slam flake failure resolving git+file:../../../..; that unrelated flake is unchanged.

AI assistance

• Review cleanup updated by OpenAI Codex (agent).
• OpenAI Codex (GPT-5) assisted extensively with implementation, tests, documentation, and stack cleanup.

Checklist

• I have read and approved the CLA.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
6047	1	6046	117

View the full list of 1 ❄️ flaky test(s)

dimos.e2e_tests.test_voice_browser::test_hold_to_talk_ships_a_decodable_recording[firefox]

Flake rate in main: 100.00% (Passed 0 times, Failed 3 times)

Stack Traces | 23.1s run time

voice_bridge = ('http://127.0.0.1:57403/', [])
fake_mic_page = <Page url='http://127.0.0.1:57403/'>

    def test_hold_to_talk_ships_a_decodable_recording(
        voice_bridge: tuple[str, list[AudioChunk]], fake_mic_page: Page
    ) -> None:
        url, chunks = voice_bridge
        chunks.clear()  # the module fixture is shared across both engines
        fake_mic_page.goto(url)
        mic = fake_mic_page.get_by_test_id("chat-audio_in-mic")
        # Enabled == transport connected; the manifest already placed the panel.
        expect(mic).to_be_enabled(timeout=120_000)
        expect(mic).to_have_attribute("data-state", "idle")
    
        mic.hover()
        fake_mic_page.mouse.down()
>       expect(mic).to_have_attribute("data-state", "recording", timeout=15_000)
E       AssertionError: Locator expected to have attribute 'recording'
E       Actual value: arming 
E       Call log:
E         - Expect "to_have_attribute" with timeout 15000ms
E         - waiting for get_by_test_id("chat-audio_in-mic")
E       
E       Aria snapshot:
E       - button "hold to talk": talk

chunks     = []
fake_mic_page = <Page url='http://127.0.0.1:57403/'>
mic        = <Locator frame=<Frame name= url='http://127.0.0.1:57403/'> selector='internal:testid=[data-testid="chat-audio_in-mic"s]'>
url        = 'http://127.0.0.1:57403/'
voice_bridge = ('http://127.0.0.1:57403/', [])

dimos/e2e_tests/test_voice_browser.py:104: AssertionError

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
dimensional	🟢 Ready	View Preview	Aug 14, 2026, 8:04 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[greptile-apps]

Greptile Summary

This change adds a host-side LeRobot policy integration backed by an isolated Python runtime, including rollout lifecycle handling and joint-command publication.

Two failures were reproduced. Standard wheel installations omit the isolated runtime manifest required to start LeRobot, so rollout startup raises FileNotFoundError. Separately, stopping a rollout can still emit one arm command and one gripper command after the stop request. These issues must be fixed before merge.

Confidence Score: 2/5

Not safe to merge because wheel-installed LeRobot rollouts cannot start and stopped rollouts can still publish robot commands.

The reproduced packaging failure blocks the feature in standard deployments, while the reproduced stop race can issue commands after a stop request.

Files Needing Attention: MANIFEST.in and dimos/imitation/policy/lerobot/python/dimos_lerobot/runtime.py

T-Rex Logs

What T-Rex did

• Executed the installed-wheel runtime-project execution script and captured its output to document the runtime path for the P1 finding.
• Executed the deterministic stop-to-publication window test and captured the output showing commands after the stop.
• Produced and documented a third finding-proof for a posted P1 finding.
• Validated the general-contract scenario by running a controlled sequence where stop_requested_before_arm_publish=True and recording the subsequent one arm and one gripper command after the stop.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Stop request can be followed by arm and gripper command publication

   • Bug
     • A deterministic controlled-hook execution reached the post-predict check with stop unset, issued _stop_policy immediately afterward, and observed an arm command plus gripper command publish while the stop event was already set.
   • Cause
     • _run_rollout checks _stop_event at lines 333-336 but performs publication later at lines 347-354 without a synchronization mechanism or a second stop check that closes the intervening window.
   • Fix
     • Serialize stop and publication with a shared lock/protocol, or perform a final stop-state check immediately before each publication while ensuring a concurrent stop cannot occur between that check and publish.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "fix(imitation): tighten LeRobot runtime ..." | Re-trigger Greptile}

[github-actions]

Backport failed for release/0.0.14, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release/0.0.14
git worktree add -d .worktree/backport/3315-to-release/0.0.14 origin/release/0.0.14
cd .worktree/backport/3315-to-release/0.0.14
git switch --create backport/3315-to-release/0.0.14
git cherry-pick -x 303d11983c2eb9f71a5c603ed269438a565969d2