Report depth export readiness in CLI snapshots
This commit is contained in:
@@ -280,7 +280,10 @@ powershell -ExecutionPolicy Bypass -File scripts\automation\apple-remote-build.p
|
||||
snapshots also feed the active frame through the shared `pp_paint_renderer`
|
||||
export-readiness report, reporting texture, transition, command, byte, and
|
||||
active-frame payload counts in `rendererUpload` JSON plus `facePngExport`
|
||||
readiness, face count, byte count, and payload count. It is covered by
|
||||
readiness, face count, byte count, and payload count. They also report
|
||||
`depthExport` readiness from the tested paint-renderer depth plan: pending
|
||||
snapshots keep it unavailable, and payload-complete snapshots expose the
|
||||
1024x1024 draw/readback plan counts. It is covered by
|
||||
`pano_cli_plan_canvas_document_snapshot_smoke` plus the payload-bearing
|
||||
snapshot smoke.
|
||||
- Live equirectangular, layer, animation-frame, and cube-face export adapters
|
||||
|
||||
@@ -551,6 +551,13 @@ agent or engineer to remove them without reconstructing context from chat.
|
||||
document snapshot before retained `Canvas::export_depth` runs. The actual
|
||||
1024x1024 perspective/depth rendering, readback, worker-thread behavior, and
|
||||
the legacy `.png` path names carrying JPEG-encoded bytes remain open.
|
||||
- 2026-06-05: DEBT-0010/DEBT-0036 were narrowed again.
|
||||
`pano_cli plan-canvas-document-snapshot` now emits the same depth export
|
||||
render-plan readiness as the live adapter. Metadata-only snapshots report
|
||||
depth export unavailable until renderer payload readback is captured;
|
||||
payload-complete snapshots report the 1024x1024 merged-face and per-layer
|
||||
depth draw counts while still marking final depth image readback as
|
||||
renderer-owned.
|
||||
|
||||
## Open Debt
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user