mirror of
https://github.com/runbear-io/beardrive.git
synced 2026-08-25 08:08:08 +02:00
3e13f0bfa5
bdrive export moves a whole project between hubs with full fidelity, and the web UI mentioned it nowhere — the answer to "why trust a hub with my files" only existed in a file a user had no reason to open. Adds one paragraph to the About card: what the archive holds (every device's journal and every blob, so full history and authorship), that bdrive import restores it into any hub, that export warns on unpushed changes, and a link to the migration docs. Copy only — no server route, no download button, no palette action. The card already sits outside every mayEdit guard, so every project member sees it; the member-role settings e2e asserts that. One correction to the reviewed plan: bdrive export takes a folder, not a project id, so the copy says to run it in the synced folder rather than leaning on the project id rendered above it. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>