Update docs for breaking method change

Author: nvsekkin

docs/source/how-to/save_camera_output.rst

@@ -21,6 +21,10 @@ directory.
 Saving using Replicator Basic Writer
 ------------------------------------
 
+.. note::
+   The BasicWriter is part of the Omniverse Replicator ecosystem and is specific to the default
+   Isaac RTX renderer backend. Other renderer backends may require different save workflows.
+
 To save camera outputs, we use the basic write class from Omniverse Replicator. This class allows us to save the
 images in a numpy format. For more information on the basic writer, please check the
 `documentation <https://docs.omniverse.nvidia.com/extensions/latest/ext_replicator/writer_examples.html>`_.

source/isaaclab/docs/CHANGELOG.rst

@@ -19,6 +19,12 @@ Changed
     ``camera.data.info[data_type]``.
   - **TiledCamera users (old):** access pattern ``camera.data.info[data_type]`` is unchanged.
 
+* **Breaking:** :meth:`~isaaclab.renderers.BaseRenderer.write_output` has been replaced by
+  :meth:`~isaaclab.renderers.BaseRenderer.read_output`. The new method receives the full
+  :class:`~isaaclab.sensors.camera.CameraData` instance and iterates output types internally.
+  Custom renderer implementations must replace ``write_output(render_data, output_name, output_data)``
+  with ``read_output(render_data, camera_data)``.
+
 Deprecated
 ^^^^^^^^^^
 

source/isaaclab/isaaclab/sensors/camera/camera_data.py

@@ -53,9 +53,6 @@ class CameraData:
     The format of the data is available in the `Replicator Documentation`_. For semantic-based data,
     this corresponds to the ``"data"`` key in the output of the sensor.
 
-    Key iteration order is not guaranteed to match the order of entries in the camera configuration's
-    ``data_types`` list; index by name or iterate ``data_types`` and look up each key explicitly.
-
     .. _Replicator Documentation: https://docs.omniverse.nvidia.com/prod_extensions/prod_extensions/ext_replicator/annotators_details.html#annotator-output
     """