Support seamless disk migration for workspace, memory and session data

[r6m9p7ccy5-cpu]

Problem

Currently Reasonix has no official way to migrate the installation and workspace projects across different disks on Windows.

1. My Reasonix is installed on drive D, and I want to move the whole application over to drive C.
2. When I move a project folder from D drive to E drive, project‑bound memory and chat sessions stop working.

Root cause

• Project‑specific memory folders are generated using SHA1 hash of the workspace absolute path. Once the folder is moved to another disk, the absolute path changes, which produces a different hash. Reasonix can no longer locate the original memory data.
• Session metadata stores the old absolute workspace path. After moving the project folder, historical chat conversations disappear from the sidebar.

Simply cutting‑and‑pasting files manually causes lost memory, missing sessions or broken recovery files. There is no official one‑click migration workflow.

Proposed solution

Hope official migration support can be added:

1. Allow migrating Reasonix installation between disks.
2. Add a built‑in Migrate Workspace tool. When users relocate a workspace folder:
   • Re‑compute memory directory hash for the new absolute path
   • Move old project memory files to the new hashed folder
   • Update workspace path inside session metadata to keep all history chats accessible
3. Avoid requiring users to manually edit JSON/config metadata files.
4. Provide documentation for cross‑disk migration steps.