docs(ecosystem): note Meta Quest lacks full-body robot control support

[jsepulveda-nvidia]

Summary

Modified 2 major documentation pages available to the public:
https://nvidia.github.io/IsaacTeleop/main/overview/ecosystem.html

• The Meta Quest 2/3/3S entry on the ecosystem/devices page did not call out that it tracks head and hands only, not full-body.
• Adds a requirements line noting it's not supported for full-body robot control, with a link to the Body Tracking guide for equipment with Motion Trackers.

https://nvidia.github.io/IsaacTeleop/main/device/body_tracking.html

• Changed the note at the top discussing the Meta skeleton and that no translation exists from it's WebXR Skeletal format.
• Remove the "Quest Body Tracking (Limited Support)" section entirely.

Test plan

• Build docs and check the Requirements panel for the Meta Quest 2 / 3 / 3S row renders as expected

Summary by CodeRabbit

• Documentation
  • Added Meta Quest compatibility guidance, noting it is not supported for full-body robot control.
  • Linked to the Body Tracking guide and recommended Motion Trackers for full-body teleoperation.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b28a2bd4-7c0a-472c-8536-4d8fa1b7d016

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 86a3ab60-a6cc-4ef6-9d2d-01177ac962ed

📥 Commits

Reviewing files that changed from the base of the PR and between 757b2bf and 98dc521.

📒 Files selected for processing (1)

• docs/source/_data/devices.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The device documentation now states that Meta Quest does not support full-body robot control. It links to the Body Tracking guide and recommends Motion Trackers for full-body teleoperation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 98dc5

This localized documentation update clarifies Meta Quest full-body robot-control limitations and links to the relevant guidance; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the documentation change: Meta Quest does not support full-body robot control.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jsepulveda/quest_docs_update

---

_{Comment @coderabbitai help to get the list of available commands.}

[yanziz-nvidia]

this means a dependency to release next version right? Instead of pre-announcing this, I think we can decouple into two parts, one is to remove the things not supported (thus just remove here); and two we can add a new PR when next version is about to merge and release and then add this description.