## Why

SCUM operations currently show player identity and vehicle snapshots, but operators cannot explain where a selected player or vehicle has been over a bounded period. A server-scoped, permission-checked map projection is needed without exposing raw logs, Companion connectivity, host data, or arbitrary coordinate queries.

## What Changes

- Define controlled SCUM Companion/log-projection events for `player.position`, `vehicle.position`, `player.vehicle.enter`, and `player.vehicle.leave`.
- Require the plugin to declare map version, coordinate conversion, sampling precision, and retention policy; project accepted events into server-isolated trajectory records.
- Add a bounded, authorized map API with time windows, player/vehicle filters, vehicle-riding segments, source/collection timestamps, and explicit missing-map/empty states.
- Add a Chinese SCUM console map view with point-and-line trajectories and links to the existing player detail and vehicle context.

## Capabilities

### New Capabilities

- `scum-map-trajectories`: Controlled collection, projection, retention, authorization, and map rendering of SCUM player and vehicle trajectories.

## Impact

- Affects platform domain/model/repository/service/validation/API DTOs and durable metadata snapshots.
- Extends the SCUM plugin manifest and schemas with bounded map metadata and semantic trajectory events.
- Adds platform-web API contracts and a shared-console map surface; it receives only safe projected coordinates and metadata.
- Does not add OCR, screen/input automation, direct game/window access, raw logs, unbounded location retention, or live heatmaps.