Clarify LEAPP export backend selection

[frlai]

Description

Previously it was unclear that there is no guarantee export is supported with all possible backends. This doc change aims to make that more clear.

Type of change

• Documentation update

Release backport

• Backport this pull request to the active release branch after it merges into develop

[isaaclab-review-bot]

Isaac Lab Review Bot

Clarifies LEAPP export-backend selection in the user documentation and argparse help, while adding the existing pt2 option to the documented backend list. The reviewed changes do not alter export behavior.

• Design and architecture: Backend selection remains centralized in add_common_export_args; no module boundaries, ownership, or export pipeline responsibilities change. The documentation now aligns its backend list with the parser choices.
• API: The --export_method name, parser default, accepted choices, and forwarding behavior are unchanged. Only its help text changes, and the documentation now includes the already-supported pt2 value.
• Implementation: The documented choices were checked against the unchanged argparse choices list and now match. The patch only changes documentation and CLI-facing explanatory text, with no package source change requiring a changelog fragment. Backend API descriptions may need future maintenance as PyTorch export APIs evolve.

No blocking issues. No inline issue met the actionable-evidence threshold; the assessment above records the review feedback.

Automated review; human maintainers own approval decisions.

[greptile-apps]

Greptile Summary

Clarifies how users should select a LEAPP policy-export backend and documents the relationship between backend choice and artifact format.

• Recommends onnx-dynamo as the default while noting model-dependent backend support.
• Documents pt2 alongside ONNX and TorchScript export formats.
• Aligns the CLI help text with the expanded backend-selection guidance.

Confidence Score: 5/5

The PR appears safe to merge because it only clarifies existing export-backend behavior and no actionable defect was identified.

The documentation and CLI help consistently recommend the existing default, explain backend-dependent compatibility, and describe the available artifact formats without changing export execution.

Important Files Changed

Filename	Overview
docs/source/policy_deployment/05_leapp/exporting_policies_with_leapp.rst	Expands backend-selection guidance and documents the pt2 artifact format without introducing a concrete documentation defect.
scripts/reinforcement_learning/leapp/export_utils.py	Clarifies the existing --export_method help text while preserving argument choices and runtime behavior.

_{Reviews (1): Last reviewed commit: "Clarify LEAPP export backend selection" | Re-trigger Greptile}

[kellyguo11]

run-ci

[kellyguo11]

run-ci