Bridge app dialog creation

docs/modernization/build-inventory.md

@@ -851,6 +851,12 @@ Known local toolchain state:
   metadata planning, progress initialization, negative progress-total clamping,
   message cancel-button/caption policy, input OK-caption propagation, and malformed
   empty OK-caption rejection without requiring legacy `Node*` dialogs.
+- `src/legacy_app_dialog_services.*` is the current app-shell bridge between
+  `pp_app_core` app dialog plans and retained `NodeProgressBar`,
+  `NodeMessageBox`, and `NodeInputBox` creation. `App::show_progress`,
+  `App::message_box`, and `App::input_box` now act as thin adapters while
+  layout insertion, callback wiring, and dialog lifetime remain tracked by
+  `DEBT-0058`.
 - `pp_app_core_app_startup_tests` covers startup run-counter increment
   planning, optional auto-timelapse/license/VR-controller decisions, negative
   and overflow run-counter rejection, stable full startup dispatch ordering,

docs/modernization/debt.md

@@ -182,6 +182,10 @@ agent or engineer to remove them without reconstructing context from chat.
   `App::show_progress`, `App::message_box`, `App::input_box`, and
   `pano_cli plan-app-dialog`, but retained `Node*` dialog creation, layout
   insertion, callback wiring, and lifetime ownership remain in the legacy app.
+  Later on 2026-06-05, retained `NodeProgressBar`, `NodeMessageBox`, and
+  `NodeInputBox` creation moved into `src/legacy_app_dialog_services.*`, making
+  the `App` methods thin adapters while retained layout/lifetime ownership
+  remains open.
 - 2026-06-05: DEBT-0043 and DEBT-0044 were narrowed. Export success,
   failure, and license-disabled dialog metadata plus export execution log
   labels now live in tested `pp_app_core` planning consumed by
@@ -261,7 +265,7 @@ agent or engineer to remove them without reconstructing context from chat.
 | DEBT-0055 | Open | Modernization | `src/app.h` now forward-declares retained iOS/macOS/Android/Linux/Web platform handles instead of including platform SDK headers, and full SDK includes are isolated in `src/platform_legacy/legacy_platform_services.cpp`, but the `App` singleton still stores those platform handles directly | Reduce central header platform coupling incrementally without rewriting non-Windows platform entrypoints before Phase 6 | Windows app build; Apple/Android/Linux/Web package smoke once platform root builds are active | Platform handles are owned by injected `pp_platform_*` shell state or services, and `App` has no platform SDK handle fields or platform conditional members |
 | DEBT-0056 | Open | Modernization | `src/asset.h` now forward-declares Android asset-manager types and uses `Asset::set_android_asset_manager` instead of public mutable manager state, but retained `Asset` still stores Android asset handles and `src/asset.cpp` still performs Android `AAssetManager` reads directly; the current `android-arm64` root preset is headless and does not expose `pp_legacy_assets_io` | Reduce legacy asset I/O header coupling without rewriting Android asset loading before the asset manager/storage boundary exists | Windows app build; `cmake --build --preset android-arm64 --target pp_assets`; Android package smoke once package builds consume shared targets | Android asset loading is owned by injected asset storage/platform services or `pp_assets` file providers, with no static Android asset manager on `Asset` |
 | DEBT-0057 | Open | Modernization | Default canvas allocation size now dispatches through `PlatformServices::default_canvas_resolution`, removing the `CANVAS_RES` platform macro from `src/canvas.h`, but WebGL's retained 512 default still lives in `src/platform_legacy/legacy_platform_services.cpp` until the Web shell owns injected services | Preserve WebGL memory behavior while moving canvas creation policy out of shared canvas headers and into the platform boundary | `pp_platform_api_tests`; `ctest --preset desktop-fast --build-config Debug -R pp_platform_api_tests`; Windows app build; WebGL package smoke once root Web build exists | Default canvas resolution is owned by injected `pp_platform_*` services for every supported platform, with no WebGL branch in the legacy fallback |
-| DEBT-0058 | Open | Modernization | App-level progress/message/input dialog metadata, including message-dialog OK/cancel captions, now consumes pure `pp_app_core` through `App::show_progress`, `App::message_box`, `App::input_box`, `pano_cli plan-app-dialog`, and `pp_app_core_app_dialog_tests`, but live execution still creates retained `NodeProgressBar`, `NodeMessageBox`, and `NodeInputBox` instances directly in `src/app_dialogs.cpp` and inserts them into the legacy layout tree | Preserve current app-shell dialog behavior while moving shared dialog policy toward UI/app services | `pp_app_core_app_dialog_tests`; `pano_cli plan-app-dialog --kind progress --total -4`; `pano_cli plan-app-dialog --kind message --cancel`; `pano_cli plan-app-dialog --kind input --ok-caption Save`; `ctest --preset desktop-fast --build-config Debug`; Windows app build | Progress/message/input dialog creation, callback wiring, layout insertion, lifetime ownership, and headless automation are owned by injected app/UI services with `App` methods acting only as adapters |
+| DEBT-0058 | Open | Modernization | App-level progress/message/input dialog metadata, including message-dialog OK/cancel captions, now consumes pure `pp_app_core` through `App::show_progress`, `App::message_box`, `App::input_box`, `pano_cli plan-app-dialog`, and `pp_app_core_app_dialog_tests`; live execution is centralized in `src/legacy_app_dialog_services.*`, but the bridge still creates retained `NodeProgressBar`, `NodeMessageBox`, and `NodeInputBox` instances and inserts them into the legacy layout tree | Preserve current app-shell dialog behavior while moving shared dialog policy toward UI/app services | `pp_app_core_app_dialog_tests`; `pano_cli plan-app-dialog --kind progress --total -4`; `pano_cli plan-app-dialog --kind message --cancel`; `pano_cli plan-app-dialog --kind input --ok-caption Save`; `ctest --preset desktop-fast --build-config Debug`; Windows app build | Progress/message/input dialog creation, callback wiring, layout insertion, lifetime ownership, and headless automation are owned by injected app/UI services with `App` methods acting only as adapters |
 
 ## Closed Debt
 

docs/modernization/roadmap.md

@@ -202,9 +202,9 @@ App-level progress, message, and input dialog metadata now also lives in
 `pp_app_core` through `plan_app_progress_dialog`,
 `plan_app_message_dialog`, and `plan_app_input_dialog`; `App::show_progress`,
 `App::message_box`, `App::input_box`, and `pano_cli plan-app-dialog` consume
-those plans before retained `NodeProgressBar`, `NodeMessageBox`, and
-`NodeInputBox` creation. Legacy dialog node lifetime/layout ownership remains
-tracked under `DEBT-0058`.
+those plans before `src/legacy_app_dialog_services.*` creates retained
+`NodeProgressBar`, `NodeMessageBox`, and `NodeInputBox` instances. Legacy
+dialog node lifetime/layout ownership remains tracked under `DEBT-0058`.
 Frame-level app decisions for the initial surface size, redraw/animation update
 gating, layout ticking, resize render-target recreation, canvas-stroke drawing,
 VR UI drawing, main UI drawing, UI observer clipping/on-screen transition/scissor
@@ -1755,6 +1755,14 @@ Results:
   input-dialog OK captions.
 - Android arm64 headless `pp_app_core`, `pano_cli`, and
   `pp_app_core_app_dialog_tests` built after the app-dialog planning slice.
+- `PanoPainter`, `pp_app_core_app_dialog_tests`, and `pano_cli` built after
+  retained progress/message/input `Node*` creation moved into
+  `src/legacy_app_dialog_services.*`.
+- Focused app-dialog CTest coverage passed again for
+  `pp_app_core_app_dialog_tests` and the `pano_cli_plan_app_dialog_*` smoke
+  tests after the legacy bridge split.
+- Android arm64 headless `pp_app_core`, `pano_cli`, and
+  `pp_app_core_app_dialog_tests` built after the app-dialog bridge split.
 - `PanoPainter`, `pp_app_core_app_startup_tests`, and `pano_cli` built after
   startup preference/runtime execution and startup resource sequencing moved
   behind app startup services.