Route SonarPen tools action through platform services

This commit is contained in:
2026-06-04 17:47:08 +02:00
parent 883be98557
commit c698de1482
11 changed files with 102 additions and 23 deletions

View File

@@ -190,9 +190,9 @@ Known local toolchain state:
menu routing, export-menu routing, main-toolbar commands, About menu
commands, and direct Tools menu commands. It keeps those live paths on the
`pp_app_core` contracts while legacy dialogs, pickers, cloud/share/export,
Tools, About, history, canvas-clear, and settings execution remain tracked by
`DEBT-0029`, `DEBT-0030`, `DEBT-0031`, `DEBT-0033`, `DEBT-0034`, and
`DEBT-0035`.
Tools, About, history, canvas-clear, settings, and platform SonarPen startup
execution remain tracked by `DEBT-0029`, `DEBT-0030`, `DEBT-0031`,
`DEBT-0033`, `DEBT-0034`, and `DEBT-0035`.
- `src/legacy_app_preference_services.*` is the current app-shell bridge for
options-menu preference execution. It keeps UI scale, viewport scale, RTL,
VR mode, VR-controller, auto-timelapse, and canvas cursor-mode callbacks on
@@ -554,8 +554,9 @@ Known local toolchain state:
callbacks, recording cleanup, exported-image publishing, persistent storage
flushing, document browse roots, native UI/window state saving, live
asset/layout reload policy, diagnostic stacktrace/crash hooks,
prepared-file writable target selection, network TLS verification policy,
and prepared-file save/download handoff; PPBR and MP4 export dialogs consume
SonarPen availability/startup, prepared-file writable target selection,
network TLS verification policy, and prepared-file save/download handoff; PPBR
and MP4 export dialogs consume
the same prepared-file policy at runtime instead of spelling mobile/Web
branches locally, layer/frame collection export dialogs consume the
work-directory collection policy before `pp_app_core` plans immediate