Plan export start decisions in app core
This commit is contained in:
@@ -413,6 +413,11 @@ Known local toolchain state:
|
||||
for image file exports, layer/frame collection directories, picked-directory
|
||||
stems, and MP4 suggested names as JSON and is covered for file, collection,
|
||||
and suggested-name states.
|
||||
- `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
|
||||
consume the same start contract before reaching legacy canvas export
|
||||
execution.
|
||||
- `pano_cli simulate-app-session` exposes `pp_app_core` project-open,
|
||||
app-close, save, save-as, save-version, and save-before-workflow decisions
|
||||
as JSON and is covered for clean, dirty, already-prompting, missing-canvas,
|
||||
@@ -423,7 +428,8 @@ Known local toolchain state:
|
||||
legacy canvas work.
|
||||
- `pp_app_core_document_export_tests` covers export file targets, collection
|
||||
directory/stem targets, picked-directory stems, MP4 suggested names, and
|
||||
invalid export naming inputs.
|
||||
invalid export naming inputs, plus export-start license/canvas availability
|
||||
decisions.
|
||||
- `pp_app_core_document_session_tests` covers clean and dirty app session,
|
||||
document-open action planning, save-request, save-before-workflow,
|
||||
new-document target/resolution/overwrite planning, document file target,
|
||||
|
||||
Reference in New Issue
Block a user