[Phase 1] Implement transaction undo/redo and revision tracking #9

New issue

Closed

opened 2026-07-25 21:52:53 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:52:53 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #8

Scope

Assign a monotonically increasing revision to accepted durable mutations.
Group one or more graph operations into transactions.
Record sufficient inverse data for add, update, remove, move, view, import, and action batches.
Implement bounded undo and redo stacks.
Reject stale expected revisions for commands that supply one.

Acceptance criteria

Every accepted transaction advances the revision exactly once.
Undo and redo restore graph data, positions, and view state deterministically.
A multi-operation batch is undone as one unit.
New edits clear the redo branch.
Tests cover stale revisions and history bounds.

Parent: #2 Depends on: #8 ## Scope - Assign a monotonically increasing revision to accepted durable mutations. - Group one or more graph operations into transactions. - Record sufficient inverse data for add, update, remove, move, view, import, and action batches. - Implement bounded undo and redo stacks. - Reject stale expected revisions for commands that supply one. ## Acceptance criteria - Every accepted transaction advances the revision exactly once. - Undo and redo restore graph data, positions, and view state deterministically. - A multi-operation batch is undone as one unit. - New edits clear the redo branch. - Tests cover stale revisions and history bounds.