← Back to parent Epic
MAZENG-FT-41 · View and restore an earlier project version
Why it matters
A user needs to inspect a historical project design safely and deliberately make it current again when necessary.
Expected outcome
Read-only historical inspection and an explicit atomic restore make version recovery understandable and auditable.
In scope
- List releases alongside the editable latest state.
- Load an exact historical release into a read-only canvas.
- Restore a confirmed release atomically while retaining its source identity.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Available releases are listed alongside the editable latest state.
- 02
Selecting a historical release loads its exact files into a read-only canvas.
- 03
Returning to latest restores normal editing.
- 04
Restoring an earlier release requires explicit confirmation and replaces the latest project data atomically.
- 05
The restored source release remains identifiable after the operation.
Dependencies and risks
Dependencies
None recorded.
Risks
- Historical use depends on stable release tags and compatible serialized resource and canvas formats.
- Legacy restoration uses object merging and two independent database writes, risking partial state.
- The legacy UI warns of irreversibility without providing a durable audit link.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.