Report depth export readiness in CLI snapshots

docs/modernization/roadmap.md

@@ -684,6 +684,11 @@ automation and live export adapters the same document/canvas-to-renderer
 readiness boundary before broader writer replacement. Live save writer
 replacement, export adoption, and renderer-owned readback remain under
 `DEBT-0010`/`DEBT-0013`/`DEBT-0036`.
+The same CLI snapshot report now emits `depthExport` readiness from
+`pp_paint_renderer::plan_document_depth_export_render`: metadata-only snapshots
+report pending renderer payload readback, while payload-complete snapshots
+report the legacy 1024x1024 depth-render draw plan and still flag the final
+3D view/depth image readback as renderer-owned.
 Live equirectangular, layer, animation-frame, and cube-face export adapters now
 prepare the same payload-bearing document snapshot and shared renderer export
 readiness report. Cube-face export writes those
@@ -2535,7 +2540,10 @@ Results:
   through `pp_paint_renderer::prepare_document_frame_export_readiness`, which
   records the renderer-neutral active-frame texture upload stream and encodes
   the composited active-frame cube faces as PNG bytes, so agents validate the
-  same document/canvas-to-renderer readiness report consumed by live export.
+  same document/canvas-to-renderer readiness report consumed by live export. It
+  also emits `depthExport` readiness from the paint-renderer depth plan, keeping
+  CLI automation aligned with the live depth export adapter while final renderer
+  readback remains retained.
 - Live image/collection/cube export adapters now prepare and log the same
   document/canvas plus shared renderer-upload and face-PNG export readiness
   reports. Cube-face export now writes the pure document/renderer PNG bytes to