Report depth export snapshot routing
This commit is contained in:
@@ -864,9 +864,11 @@ powershell -ExecutionPolicy Bypass -File scripts\automation\apple-remote-build.p
|
||||
that decides whether payload-complete document snapshots use pure
|
||||
document/renderer export writers or retained legacy exporters, including
|
||||
PNG/JPEG equirectangular target support, collection/cube target support,
|
||||
platform unsupported, and pending renderer-readback fallback reasons. The
|
||||
live retained export bridge consumes the same current-platform support helper
|
||||
for snapshot-writer attempts instead of carrying local Web writer gates.
|
||||
depth unsupported-target fallback, platform unsupported, and pending
|
||||
renderer-readback fallback reasons. The live retained export bridge consumes
|
||||
the same current-platform support helper for snapshot-writer attempts instead
|
||||
of carrying local Web writer gates, and depth export logs that route fallback
|
||||
before retained depth rendering.
|
||||
- `pano_cli plan-export-start` exposes `pp_app_core` export availability
|
||||
planning for license-gated, demo-blocked, and missing-canvas states as JSON;
|
||||
the live image, layer, animation-frame, depth, and cube-face export dialogs
|
||||
|
||||
Reference in New Issue
Block a user