Lite v1 / 03 Dispatch — local persistence and no cloud sync

[evanqua]

Summary

Implement Lite dispatch using local storage as the source of truth, reusing existing dispatch UI patterns while removing cloud sync and map/recap dependencies.

Motivation

Lite dispatch is the core operational requirement. It must support real-time local workflow without backend writes and without requiring summary/map flows.

Proposed solution

• Add /lite/events/[localEventId]/dispatch.
• Reuse existing dispatch components where possible, but replace cloud transactions/snapshots with local read/write adapter calls.
• Persist all dispatch changes locally (calls, team status/location, supervisor changes, equipment changes, logs).
• Disable or remove map-related entry points in Lite dispatch.
• Remove recap dependency in Lite flow (CSV export handled separately).
• Handle missing/invalid local event ID gracefully (prompt to create new Lite event).

Alternatives considered

• Keep cloud dispatch page and swap only persistence layer. Rejected for v1 due to extensive auth/cloud assumptions in current route.
• Build entirely new dispatch UI for Lite. Rejected for v1 due to unnecessary duplication.

Mockups / Examples

• User loads /lite/events//dispatch
• Dispatch actions update immediately and remain after refresh
• No login prompts and no cloud sync required

Acceptance criteria

• Lite dispatch performs all event updates locally.
• Page reload restores active local event state.
• No Firebase/Auth/Firestore/DataConnect requests for Lite dispatch data.
• Map/summary-only controls are hidden or disabled in Lite mode.
• Existing cloud dispatch remains unchanged.

Priority

High

Additional context

Parent Issue: #1
Depends on: #3