Expose recording renderer through pano cli

docs/modernization/build-inventory.md

@@ -244,6 +244,8 @@ Known local toolchain state:
 - `pp_renderer_api` exposes a headless `RecordingRenderDevice` that validates
   command order, records render commands, and records trace markers without a
   window or GL context.
+- `pano_cli record-render` exposes the recording renderer through JSON
+  automation and is covered by `pano_cli_record_render_smoke`.
 - `pp_ui_core` consumes vcpkg tinyxml2 only when `PP_USE_VCPKG_TINYXML2=ON`
   through the vcpkg preset; default and Android validation still use the
   retained vendored fallback tracked by DEBT-0012.

docs/modernization/roadmap.md

@@ -743,6 +743,9 @@ Results:
 - `pp_renderer_api` now includes a headless `RecordingRenderDevice` with strict
   command-order validation and command/trace capture, giving automation a
   backend-neutral render path that does not require a window or GL context.
+- `pano_cli record-render` exercises that headless recording renderer and emits
+  JSON command counts, target dimensions, backend name, and trace/draw summary
+  for agent automation.
 - PowerShell package-smoke wrapper validates the Windows CMake app executable
   and runtime `data/` copy.
 - Android arm64 configured with NDK 29.0.14206865 through the platform-build