Use the desktop Sync Changes workspace for project incoming/outgoing review and history. Project sync is separate from design-file Undo, local/Git export, and session-only MCP activity marks.
Refresh sync status and review incoming changes first. The current push action remains disabled while incoming work exists. Inspect files changed on both sides, apply/resolve the intended current state, rerun affected Preview/build checks, then review the outgoing set.
Expand the file and nested node/property rows. Open the comparison and inspect before/after values; collapsed ancestors can summarize descendant changes.
Compare the historical entry with its parent and the live project. When uncertain, copy or duplicate the historical file beside the live file and inspect it. In-place Restore This Version or Discard My Changes writes historical content into the live project as a new outgoing change; it does not rewrite history.
Use the history action that restores a deleted file as a copy. Then review references and outgoing changes before pushing.
Design-file Undo moves through eligible content history; it is not a project-sync rollback. Use sync history and current comparison to plan recovery. Do not assume export or remote Git history matches Misaki project history.
Stop overlapping structural work, refresh, and reread the affected file before another write. Assign one owner to the conflict resolution and retest dependents after merging.