Build the export UI with pre-flight review and progress #34

New issue

Open

opened 2026-07-28 04:57:31 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-28 04:57:31 +00:00

Context

Export is admin-triggered, long-running, and writes files the user keeps. It needs a UI
that makes the consequences clear before it starts and observable while it runs.

Scope

The export configuration, pre-flight review, and progress UI.

Implementation notes

Configuration step: export mode, output directory, overwrite policy, lossless option.
Render the pre-flight report before anything is written, with exclusion counts and
reasons broken out. The confirm action should require the user to have actually seen
what will be excluded â€” this is the last point at which a mistake is cheap to correct.
Blocking conditions disable the confirm action and explain how to resolve them.
Live progress: files completed, current file, estimated time remaining, and a cancel control.
Cancel must leave a clearly labelled partial state with its manifest, and say plainly
that the export is incomplete.
Completion summary with counts, output location, and a link to the manifest.
Failures surface the actual error â€” particularly a hash verification mismatch, which
indicates data corruption and deserves prominent, unambiguous alerting rather than a
generic failure toast.
Export history so previous runs and their outcomes remain visible.

Done when

Export can be configured and launched by an admin
The pre-flight report is shown and acknowledged before execution
Progress and cancellation work during a long run
Hash mismatches are alerted prominently and distinctly
Past export runs and their manifests remain accessible

References

docs/circa-spec.md section 12
docs/circa-ui-spec.md

Depends on: export pre-flight checks, export execution, manifest generation.

## Context Export is admin-triggered, long-running, and writes files the user keeps. It needs a UI that makes the consequences clear before it starts and observable while it runs. ## Scope The export configuration, pre-flight review, and progress UI. ## Implementation notes - Configuration step: export mode, output directory, overwrite policy, lossless option. - Render the pre-flight report before anything is written, with exclusion counts and reasons broken out. The confirm action should require the user to have actually seen what will be excluded â€” this is the last point at which a mistake is cheap to correct. - Blocking conditions disable the confirm action and explain how to resolve them. - Live progress: files completed, current file, estimated time remaining, and a cancel control. - Cancel must leave a clearly labelled partial state with its manifest, and say plainly that the export is incomplete. - Completion summary with counts, output location, and a link to the manifest. - Failures surface the actual error â€” particularly a hash verification mismatch, which indicates data corruption and deserves prominent, unambiguous alerting rather than a generic failure toast. - Export history so previous runs and their outcomes remain visible. ## Done when - [ ] Export can be configured and launched by an admin - [ ] The pre-flight report is shown and acknowledged before execution - [ ] Progress and cancellation work during a long run - [ ] Hash mismatches are alerted prominently and distinctly - [ ] Past export runs and their manifests remain accessible ## References - `docs/circa-spec.md` section 12 - `docs/circa-ui-spec.md` Depends on: export pre-flight checks, export execution, manifest generation.

claude-bot added this to the v0.5.0 milestone

2026-07-28 04:57:31 +00:00

claude-bot added the

frontend

enhancement

labels

2026-07-28 04:57:31 +00:00