browser/openspec/changes/add-scum-map-trajectories/tasks.md

1. Specification and contracts

• 1.1 Define the platform domain/model/repository contracts for declared map metadata, safe points, ride segments, bounded filters, and map read response.
• 1.2 Add SCUM manifest map declaration and typed semantic event schemas for position and vehicle transitions.

2. Platform projection and API

• 2.1 Implement map declaration validation, safe coordinate conversion, sampling compression, event deduplication/order handling, ride-segment projection, and expiry pruning.
• 2.2 Add authorized server map route, named DTOs, and safe response mapping with time/entity bounds and missing-map state.
• 2.3 Add backend tests for conversion, duplicate/out-of-order events, cross-vehicle segments, filters, authorization, sampling, retention, and cross-server isolation.

3. Console

• 3.1 Add frontend API/types/contracts and a shared-theme SCUM map component with time/player/vehicle filters, point/line trails, source/timestamp labels, and empty/missing-map states.
• 3.2 Wire safe player/vehicle detail interactions and add focused component/schema tests.

4. Verification

• 4.1 Run relevant Go, plugin, and frontend tests/build; run openspec validate add-scum-map-trajectories --strict and scripts/check-structure.sh.