[Docs] Fix environment browser task scopes

[StafaH]

Description

Fix the environments-page command builder and task browser:

• Make the pre-trained checkpoint control actionable from Train by switching the command to Play, and disable it for Contrib and Warp.
• Add a Core / Contrib / Warp task-collection switch beside the task picker and use it to partition both the picker and available-task list.
• Derive Warp-compatible tasks from the same frontend compatibility path used at runtime, keep canonical task IDs, and emit --frontend warp.
• Align the --task dropdown with the physics selector below it.

Type of change

• Bug fix
• Documentation update

Validation

• uv run isaaclab -f
• uv run python -m pytest --confcutdir=tools/test tools/test/test_environ_docs.py::test_environment_browser_rows_include_concrete_core_and_contributed_selectors
• uv run --isolated --extra test -- make -C docs current-docs
• node --check docs/source/_static/css/environment-browser.js
• Headless Chrome interaction check for Core, Contrib, Warp, and pre-trained checkpoint command generation

The full tools/test/test_environ_docs.py file has one unrelated existing failure in test_physics_names_for_docs_infers_physx_from_default; the focused environment-browser metadata test passes.

Checklist

• I have read and understood the contribution guidelines
• I have run the pre-commit checks
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added focused coverage for the generated Warp metadata
• No source package was changed, so no package changelog fragment is required
• My name already exists in CONTRIBUTORS.md

[greptile-apps]

Greptile Summary

The PR partitions the environment browser into Core, Contrib, and Warp collections, derives Warp compatibility during documentation generation, and changes the checkpoint control to switch commands from Train to Play.

• Adds collection-scoped task pickers and browser lists.
• Generates canonical Warp-compatible task metadata and --frontend warp commands.
• Updates command-builder styling, checkpoint behavior, and focused documentation-generation tests.

Confidence Score: 3/5

The PR should not merge until Warp scope constrains incompatible physics choices and checkpoint controls reflect actual published-checkpoint availability.

The browser currently generates commands that deterministically fail when Warp is paired with an offered PhysX backend and can generate checkpoint commands that terminate without launching for unsupported task, library, or backend combinations.

Files Needing Attention: docs/source/_static/css/environment-browser.js

Important Files Changed

Filename	Overview
docs/source/_static/css/environment-browser.js	Adds collection-scoped browser state and command generation, but allows invalid Warp/physics combinations and enables unavailable pre-trained checkpoints.
tools/environ_docs.py	Adds Warp compatibility derivation and serialization to generated browser metadata.
docs/source/setup/environments.rst	Adds the Core, Contrib, and Warp collection controls and removes the redundant Contrib category.
docs/source/_static/css/environment-browser.css	Styles the new collection switch, aligned task label, and disabled checkpoint control.
tools/test/test_environ_docs.py	Extends generated-row coverage to include Warp compatibility metadata, without exercising the browser command combinations implicated above.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Scope["Collection scope"] --> Tasks["Scoped task metadata"]
  Tasks --> Selectors["Task / RL / physics selectors"]
  Scope --> Command["Command builder"]
  Selectors --> Command
  Command --> CLI["isaaclab play/train"]
  CLI --> Frontend["Selected frontend"]
  CLI --> Checkpoint["Published checkpoint lookup"]

Loading

_{Reviews (1): Last reviewed commit: "Fix environment browser task scopes" | Re-trigger Greptile}

[isaaclab-review-bot]

Isaac Lab Review Bot

The Core/Contrib/Warp partition and generated Warp metadata are integrated coherently, but the browser can emit Warp commands with physics configurations that were never checked for Warp compatibility, and the Warp scope handler fails when generation produces no compatible tasks.

• Design and architecture: Warp eligibility is calculated only after applying the newton_mjwarp preset, while Warp scope leaves all task physics choices available and always emits --frontend warp. Constrain Warp scope to the configuration used for compatibility determination, or validate eligibility against the selected physics configuration.
• API: The added positional supportsWarpFrontend metadata is padded and consumed consistently, and the RST scope controls match the JavaScript selectors. The remaining command-builder contract ambiguity is that selecting Warp communicates compatibility even when the generated command uses an unchecked physics preset.
• Implementation: The scope transition logic assumes every scope contains at least one task. Because compatibility discovery intentionally converts import or registry failures into False, regeneration can produce an empty Warp collection and scopedTasks[0].task will throw. Empty scopes should be guarded or disabled.

Minor fixes needed. Posted 2 actionable findings inline.

Automated review; human maintainers own approval decisions.

[AntoineRichard]

LGTM, though my AI mentioned the following:

  - Important: docs/source/_static/css/environment-browser.js:672 — switching to Warp
    retains a previously selected non-Warp physics preset. For example, select
    isaacsim_physx in Core, then select Warp: the command includes --frontend warp
    physics=isaacsim_physx, which is incompatible. Force or restrict the physics selector
    to newton_mjwarp when entering Warp scope.

  Review Coverage

  Reviewed all changed JS/CSS, Python generator, RST, and tests. No other high-confidence
  findings. Pytest could not start in this sandbox due to its network-namespace