Add file menu service boundary

This commit is contained in:
2026-06-03 13:00:22 +02:00
parent defa9fc212
commit e880f23040
5 changed files with 266 additions and 42 deletions

View File

@@ -522,8 +522,9 @@ legacy `Canvas::import_equirectangular` or import transform-mode execution
continues.
`pano_cli plan-file-menu` exposes app-core planning for the top-level File menu
commands, including new/open/import, save/save-as/save-version, share, resize,
cloud upload/browse, JPEG export, and export-submenu routing before legacy
dialogs, pickers, platform services, cloud code, and canvas workflows continue.
cloud upload/browse, JPEG export, and export-submenu routing. Direct File menu
commands now dispatch through `FileMenuServices` before legacy dialogs, pickers,
platform services, cloud code, and canvas workflows continue.
`pano_cli plan-export-menu` exposes app-core planning for File menu export
choices, including image, layer, cube-face, depth, animation-frame, MP4, and
timelapse dialog routing plus license/canvas gating before legacy export dialogs
@@ -1245,7 +1246,8 @@ Results:
> Import route planning as JSON automation.
- `pp_app_core_file_menu_tests` passed, covering top-level File menu routing for
creation/open/import, save intents, export/submenu/cloud actions, and unknown
command rejection.
command rejection, plus executor dispatch for dialog, picker, save, export,
share, resize, and cloud actions.
- `pano_cli_plan_file_menu_import_smoke`,
`pano_cli_plan_file_menu_save_as_smoke`,
`pano_cli_plan_file_menu_export_smoke`,