Persist project device synchronization

This commit is contained in:
2026-07-24 11:47:03 +02:00
parent e930cb75b8
commit 3977a6e6e1
20 changed files with 300 additions and 747 deletions
+7 -4
View File
@@ -415,16 +415,19 @@ Implemented foundation:
previously linked rows only from complete unchanged disconnected snapshots
- ProjectDevice create, update, delete and global-to-project copy endpoints use
these commands, require `expectedRevision` and return the new history state
- ProjectDevice synchronization and disconnect endpoints also require
`expectedRevision`; their UI undo uses project-wide persistent history and
the obsolete direct restore/reconnect write paths are removed
- revision metadata, change-set payloads and the project counter are committed
in one SQLite transaction
- a stale expected revision produces no history writes
- integration coverage verifies sequential revisions, stale-command rejection
and rollback after a forced late persistence failure
ProjectDevice CRUD on the project page is connected to this history boundary.
The circuit-list editor and the remaining domain writes are not fully connected;
its visible undo/redo therefore remains session-local until the remaining tasks
are implemented.
ProjectDevice CRUD, synchronization and disconnect on the project page are
connected to this history boundary. The circuit-list editor and the remaining
domain writes are not fully connected; its visible undo/redo therefore remains
session-local until the remaining tasks are implemented.
Acceptance criteria: