Summary
Add Lite end-of-event data handling: export dispatch logs to CSV and provide clear wipe-local-data controls, without requiring a summary/recap page.
Motivation
Lite mode needs a practical endpoint: keep data local during operations, then export and clear when desired. This satisfies privacy-first workflows without backend storage.
Proposed solution
- Add CSV export action in Lite dispatch/end-event flow.
- Reuse/align with existing log export columns where feasible.
- Add local data wipe controls:
- Wipe current Lite event
- Wipe all Lite mode data
- Add clear UX messaging before destructive wipe.
- After wipe, route back to Lite landing/start flow.
- Keep recap/summary page out of Lite v1 scope.
Alternatives considered
- Require summary page for export. Rejected because Lite v1 explicitly avoids recap flow.
- Auto-delete data at end event with no prompt. Rejected due to risk of accidental loss.
Mockups / Examples
- User selects “End Lite Event”
- User exports CSV
- User chooses to wipe current/all local Lite data
- App returns to /lite
Acceptance criteria
- CSV export downloads valid event/dispatch log data for Lite events.
- Wipe actions delete targeted Lite data from browser storage.
- Wiped events cannot be reopened.
- No backend requests are made for Lite export/wipe operations.
- Cloud mode export/summary behavior remains unchanged.
Implementation notes (optional)
- Suggested files, components, or areas to change (helpful for contributors).
- Any API/DB schema considerations.
Priority
High
Additional context
Parent Issue: #1
Depends on: #4
Summary
Add Lite end-of-event data handling: export dispatch logs to CSV and provide clear wipe-local-data controls, without requiring a summary/recap page.
Motivation
Lite mode needs a practical endpoint: keep data local during operations, then export and clear when desired. This satisfies privacy-first workflows without backend storage.
Proposed solution
Alternatives considered
Mockups / Examples
Acceptance criteria
Implementation notes (optional)
Priority
High
Additional context
Parent Issue: #1
Depends on: #4