`MAZENG-FT-21` · Save, inspect, and restore design versions

Feature intent

Users need to preserve named design versions, inspect history safely, and deliberately restore an earlier design.

Why it matters

Users need to preserve named design versions, inspect history safely, and deliberately restore an earlier design.

Users can recover and compare design state without silently mutating historical versions or losing the selected revision.

Create an identifiable named version containing complete resource configuration and canvas presentation.
Open a historical version in a clearly identified read-only mode.
Restore a historical version only after explicit confirmation, atomically replacing current design state while retaining history.

Acceptance

01
Saving captures the complete resource configuration and canvas presentation under an identifiable version.
02
Opening a historical version is read-only and clearly identifies the version being viewed.
03
Restoring a historical version requires explicit confirmation, replaces the current design atomically, and preserves the historical version.

None recorded.

Version capture integrity is unproven in the legacy release path and must not be assumed from an empty release object.
A non-atomic restore could combine resource data from one revision with canvas data from another.

No authoritative Architecture tasks are linked.