Move project save commit planning to app core
This commit is contained in:
@@ -712,7 +712,10 @@ path planner for target, temporary PPI, and timelapse sidecar paths; live
|
||||
app-core boundary now also plans the retained save write mode, distinguishing
|
||||
direct first saves from existing-target temporary writes that swap into place
|
||||
and preserving the legacy direct-write fallback when the temporary file cannot
|
||||
be opened. The same automation now feeds payload-complete snapshots through the
|
||||
be opened. The same app-core boundary now also classifies the post-write
|
||||
commit result for direct writes, successful temporary swaps, remove failures,
|
||||
and rename-after-remove failures before retained save metadata mutation
|
||||
continues. The same automation now feeds payload-complete snapshots through the
|
||||
shared
|
||||
`pp_paint_renderer::prepare_document_frame_export_readiness` report, which
|
||||
records renderer-neutral six-face texture upload commands and encodes the
|
||||
@@ -2320,6 +2323,9 @@ Results:
|
||||
It also reports the app-core write-mode plan for direct first saves versus
|
||||
existing-target temporary writes, including the retained fallback to direct
|
||||
target writes when the temporary file cannot be opened.
|
||||
The command now reports the app-core commit plan for direct saves, successful
|
||||
temporary swaps, target-remove failures, and rename-after-remove failures,
|
||||
including whether the target may be missing after a failed swap.
|
||||
- The same payload-complete snapshot automation now uploads the active document
|
||||
frame through `pp_paint_renderer::upload_document_frame_faces` and the
|
||||
`RecordingRenderDevice`, emitting `rendererUpload` JSON with texture,
|
||||
|
||||
Reference in New Issue
Block a user