Expose image import simulation through pano cli

This commit is contained in:
2026-06-02 09:59:42 +02:00
parent 1e4b4cad73
commit 3701fd2a71
4 changed files with 152 additions and 1 deletions

View File

@@ -118,6 +118,9 @@ Known local toolchain state:
- `pano_cli simulate-document-history` exercises pure document history
apply/undo/redo behavior and is covered by
`pano_cli_simulate_document_history_smoke`.
- `pano_cli simulate-image-import` decodes an embedded tiny PNG through
`pp_assets`, attaches it to `pp_document`, and is covered by
`pano_cli_simulate_image_import_smoke`.
- `pano_cli simulate-stroke` exposes the pure stroke sampler for scripted
automation and is covered by `pano_cli_simulate_stroke_smoke`.
- `pano_cli simulate-stroke-script` loads a text stroke script fixture and is
@@ -257,6 +260,10 @@ Known local toolchain state:
- `pano_cli simulate-document-edits` exposes `pp_document` layer metadata,
frame order, active-index, and tiny face-payload state through JSON
automation and is covered by `pano_cli_simulate_document_edits_smoke`.
- `pano_cli simulate-image-import` exposes embedded PNG decode and document
face-payload attachment through JSON automation and is covered by
`pano_cli_simulate_image_import_smoke`; full file import/export remains a
future CLI automation task.
- `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.