Add multi-layer PPI save automation

This commit is contained in:
2026-06-02 10:32:10 +02:00
parent 4e70c90ca8
commit e6e80b94ba
9 changed files with 151 additions and 49 deletions

View File

@@ -115,7 +115,7 @@ Known local toolchain state:
frame counts, durations, and decoded face-pixel payloads when present; the
metadata-only minimal fixture remains covered by
`pano_cli_load_project_metadata_smoke`.
- `pano_cli save-project` writes single-layer multi-frame PPI files through
- `pano_cli save-project` writes generated multi-layer, multi-frame PPI files through
`pp_assets` and is covered by `pano_cli_save_project_roundtrip_smoke` and
`pano_cli_save_project_payload_roundtrip_smoke`, which reload generated
metadata-only and dirty-face-payload projects through `pano_cli load-project`.
@@ -275,9 +275,9 @@ Known local toolchain state:
face-payload attachment through JSON automation and is covered by
`pano_cli_import_image_rejects_truncated_png`; a checked-in decodable image
fixture and export/round-trip automation remain future CLI tasks.
- `pano_cli save-project` exposes single-layer multi-frame PPI writing through JSON
- `pano_cli save-project` exposes generated multi-layer, multi-frame PPI writing through JSON
automation and is covered by metadata-only and dirty-face-payload round-trip
smoke tests; full multi-layer legacy canvas save parity remains tracked by
smoke tests; full legacy canvas save parity remains tracked by
DEBT-0013.
- `pp_ui_core` consumes vcpkg tinyxml2 only when `PP_USE_VCPKG_TINYXML2=ON`
through the vcpkg preset; default and Android validation still use the