Docs update
Some checks failed
CI / React UI Build (push) Successful in 11s
CI / Native Windows Build And Tests (push) Failing after 2m11s
CI / Windows Release Package (push) Has been skipped

This commit is contained in:
2026-05-21 17:14:29 +10:00
parent 5c46eaf18a
commit 3fc78d5bb8
7 changed files with 204 additions and 559 deletions

View File

@@ -263,14 +263,13 @@ Recommended direction:
Status: addressed by Phase 6.
Relevant code:
Relevant current `RenderCadenceCompositor` code:
- `RuntimeCoordinator.cpp`
- `RuntimeUpdateController.cpp`
- `RuntimeStore.cpp`
- `PersistenceWriter.cpp`
- `src/app/RuntimeLayerControllerControls.cpp`
- `src/runtime/RuntimeStatePersistence.cpp`
- `src/runtime/RuntimeStatePersistence.h`
Runtime-state persistence now flows from accepted coordinator mutations to typed persistence events, then into a debounced background writer. The store still owns serialization and preset IO, while the writer owns temp-file replacement, coalescing, result reporting, and shutdown flushing.
Runtime-state persistence now flows from accepted durable layer-stack mutations into a debounced background writer. The layer controller owns the current snapshot source, while `RuntimeStatePersistenceWriter` owns serialization, temp-file replacement, coalescing, result reporting, and shutdown flushing.
The remaining architecture concern is broader persistence policy, not direct mutation-path disk writes: