Route live save snapshots through PPI policy
This commit is contained in:
@@ -524,8 +524,16 @@ agent or engineer to remove them without reconstructing context from chat.
|
||||
Save, Save As, Save Version, and save-before-workflow now prepare a
|
||||
payload-bearing canvas document snapshot plus `pp_app_core` save-readiness
|
||||
report before delegating to retained `Canvas::project_save`. The retained
|
||||
writer still owns PPI serialization, progress/threading, and compatibility
|
||||
quirks, so pure writer replacement remains open.
|
||||
writer still owned PPI serialization, progress/threading, and compatibility
|
||||
quirks, so pure writer replacement remained open.
|
||||
- 2026-06-06: DEBT-0010/DEBT-0013/DEBT-0040/DEBT-0042 were narrowed again.
|
||||
`pp_app_core` now owns a tested save-writer route policy for canvas snapshots,
|
||||
`pano_cli plan-canvas-document-snapshot` emits that route as JSON, and live
|
||||
Save, Save As, Save Version, and save-before-workflow run the pure PPI
|
||||
exporter for payload-complete snapshots and log byte counts before retained
|
||||
`Canvas::project_save` continues. The retained writer still owns actual save
|
||||
serialization, app metadata mutation, progress/threading, and compatibility
|
||||
quirks.
|
||||
- 2026-06-05: DEBT-0010/DEBT-0013 were narrowed again. `pp_app_core` now
|
||||
exports payload-complete or metadata-only canvas document snapshots through
|
||||
the pure `pp_document` PPI writer and rejects snapshots that still require
|
||||
|
||||
Reference in New Issue
Block a user