[Phase 5] Add secure local file workflows and recovery #32

New issue

Closed

opened 2026-07-25 21:56:58 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:56:58 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #10, #11, #30, #31

Scope

Add drag-and-drop and browser file-picker workflows for graph, table, evidence, and trace imports.
Use the File System Access API only as an optional enhancement with standard download/upload fallback.
Add explicit backup, restore, workspace bundle export, and recovery import flows.
Detect unsaved changes, interrupted imports, quota pressure, and missing local blobs.
Add periodic user-controlled backup reminders without background uploads.

Acceptance criteria

Core file workflows work without privileged browser APIs.
Restore creates or replaces a workspace only after validation and confirmation.
Recovery never depends on a remote service.
Large imports stream or use workers instead of blocking the main thread.
Workspace bundles include manifests and referenced local assets with integrity checks.

Parent: #2 Depends on: #10, #11, #30, #31 ## Scope - Add drag-and-drop and browser file-picker workflows for graph, table, evidence, and trace imports. - Use the File System Access API only as an optional enhancement with standard download/upload fallback. - Add explicit backup, restore, workspace bundle export, and recovery import flows. - Detect unsaved changes, interrupted imports, quota pressure, and missing local blobs. - Add periodic user-controlled backup reminders without background uploads. ## Acceptance criteria - Core file workflows work without privileged browser APIs. - Restore creates or replaces a workspace only after validation and confirmation. - Recovery never depends on a remote service. - Large imports stream or use workers instead of blocking the main thread. - Workspace bundles include manifests and referenced local assets with integrity checks.