Stop Isaac Lab emitting Kit deprecation tracebacks, and drop the deprecated API we still called

[hujc7]

Description

Two related halves of nvbug 6585535.

1. Isaac Lab's app experiences never suppressed developer warnings. They were adapted from isaacsim.exp.base.kit but did not carry over its enableDeveloperWarnings = false. All 9 Isaac Sim experiences set it "to reduce log noise"; all 6 of ours did not, and Isaac Lab always launches its own experience (app_launcher.py:1180-1200). carb.deprecated() logs at warning level only when that setting is truthy and formats each message with a Callstack: block, so routine Kit deprecation notices appeared as traceback-shaped text that QA automation cannot separate from real errors.

It has to be set at app boot: _create_app() builds SimulationApp before _load_extensions() runs, so Isaac Lab's central carb settings block is too late. The experience files are the only hook early enough. Suppressed diagnostics stay available per run via --kit_args "--/app/enableDeveloperWarnings=true".

2. We were still calling a deprecated Kit API. IApp.get_post_update_event_stream was the last one, at 7 call sites. They now register through the simulation context's visualization marker registry — the mechanism assets, sensors and the non-experimental managers already use. The two isaaclab_experimental managers were byte-for-byte copies of their core twins from before those were migrated.

This also fixes debug visualization in kitless mode: omni.kit.app was imported only when Kit is present but referenced unconditionally, so enabling debug vis without Kit raised NameError: name 'omni' is not defined (direct envs) or ModuleNotFoundError: No module named 'omni.kit' (Warp-frontend managers).

Behaviour change: debug-vis callbacks now run when a marker-capable visualizer dispatches them instead of on every Kit post-update tick, matching the existing registry call sites.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Screenshots

play.py --rl_library rsl_rl --task Isaac-Reach-UR10 --visualizer kit (resolves to isaaclab.python.kit):

	before	after
Warnings carrying a Callstack: block	3	0
All [Warning] lines	35	5

The 3 are the ones in the bug: get_update_event_stream (x2) and get_stage_event_stream from omni.graph.visualization.nodes.

Kitless regression, all five affected classes, before → after: NameError/ModuleNotFoundError → registers and clears cleanly. Covered by test_set_debug_vis_registers_without_kit, which fails on develop with NameError: name 'omni' is not defined.

Checklist

• I have run the pre-commit checks with ./isaaclab.sh --format
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have updated the changelog and the corresponding version in the extension's config/extension.toml file
• I have added my name to the CONTRIBUTORS.md or my name already exists there

[greptile-apps]

Greptile Summary

The PR disables Kit developer warnings at boot across every Isaac Lab experience selected by AppLauncher, reducing traceback-shaped deprecation noise while retaining the documented command-line override.

• Adds /app/enableDeveloperWarnings = false to the standard GUI experience.
• Applies the same default to headless, rendering, and OpenXR variants.
• Preserves per-run re-enablement through --kit_args.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

All six launcher-selected experiences consistently configure the same Kit setting, and the command-line path for explicitly re-enabling developer warnings remains available.

Important Files Changed

Filename	Overview
apps/isaaclab.python.headless.kit	Disables developer warnings in the default non-rendering headless experience without changing its existing warning-level logging configuration.
apps/isaaclab.python.headless.rendering.kit	Applies the same developer-warning default to the camera-enabled headless experience.
apps/isaaclab.python.kit	Disables developer warnings in the standard GUI experience through its existing [settings.app] section.
apps/isaaclab.python.rendering.kit	Applies the developer-warning default to the GUI rendering experience.
apps/isaaclab.python.xr.openxr.headless.kit	Applies the developer-warning default to the headless OpenXR experience.
apps/isaaclab.python.xr.openxr.kit	Applies the developer-warning default to the GUI OpenXR experience.

_{Reviews (1): Last reviewed commit: "Disable Kit developer warnings in Isaac ..." | Re-trigger Greptile}

[isaaclab-review-bot]

Isaac Lab Review Bot

The change consistently disables Kit developer warnings at boot across all six Isaac Lab experience files, reducing callstack-shaped deprecation noise while retaining an explicit configuration surface for diagnostics.

• Design and architecture: The experience-level setting is an appropriately early and narrowly scoped design choice. Repeating it in derived rendering and XR experiences is somewhat redundant with inheritance, but ensures consistent behavior for every directly launched experience.
• API: No Python symbols, CLI arguments, or package interfaces are changed. The configuration default changes warning visibility, but the underlying Kit setting remains available for per-run overrides. No source-package changelog fragment is required for these app-only edits.
• Implementation: Each assignment uses the correct nesting for its file: dotted app.enableDeveloperWarnings keys in flat [settings] tables and enableDeveloperWarnings under [settings.app] in isaaclab.python.kit. The implementation is minimal and consistent. The non-blocking tradeoff is that developer deprecation diagnostics are hidden by default and must be explicitly re-enabled during investigation.

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.