Route PPBR export directory policy through platform services

This commit is contained in:
2026-06-04 18:01:50 +02:00
parent 148aceb705
commit 52cf7628da
10 changed files with 64 additions and 14 deletions

View File

@@ -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,
SonarPen availability/startup, prepared-file writable target selection,
network TLS verification policy, and prepared-file save/download handoff; PPBR
SonarPen availability/startup, PPBR export data-directory policy,
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
@@ -699,12 +700,15 @@ Known local toolchain state:
between `pp_app_core` PPBR brush package export requests and live
`NodePanelBrushPreset::export_ppbr` execution. It preserves dialog metadata,
the retained legacy `Image` header object, desktop worker-thread export,
mobile/Web save completion, dialog lifetime, and success messages while brush
asset/storage/UI/platform ownership is tracked by `DEBT-0047`.
mobile/Web save completion, dialog lifetime, and success messages while the
PPBR preview data-directory override now comes from `PlatformServices`;
remaining brush asset/storage/UI/platform ownership is tracked by
`DEBT-0047`.
- `src/assets/brush_package.*` owns the first headless PPBR package helpers:
header validation, legacy-compatible version acceptance, export path
normalization, preview-data-directory planning, and imported brush
tip/pattern image target paths. Live
tip/pattern image target paths. Live export maps the active platform PPBR
data-directory policy into these helpers, and live
`NodePanelBrushPreset::export_ppbr`/`import_ppbr` and ABR import image writes
consume these helpers, but legacy Serializer/Image payload parsing, preview
rendering, preset storage, duplicate policy, and strict-version cleanup remain