Exploration tracker: live scan values, session distance travelled, body details #187

Goal

Show what a scanning/mapping session is worth as it happens, and the facts about a body without opening the system map.

Scope

• Running total of estimated scan and mapping payouts for the current session and system, from Scan, SAAScanComplete, FSSAllBodiesFound, including first-discovery / first-mapped flags (WasDiscovered, WasMapped). The payout formulas must be derived and documented in our own words with sources in a SOURCES.md, and tested against known examples.
• Distance travelled this session (jump distances from FSDJump), jumps count, systems visited.
• A body details panel (class, mass, gravity, atmosphere, temperature, volcanism, signals, landable) from the latest Scan of the selected/nearest body.
• Card on the dashboard; optional overlay line. Respect the "uploaded data" boundaries: nothing new is sent anywhere.

Acceptance criteria

• Totals match worked examples for each body type and the discovery/mapping multipliers.
• Session totals reset on a clear new session, not on every relog.
• Parsing is defensive for missing fields; replayed history does not double count.

Part of the epic #182.

Clean-room: see the rule on the epic. No SrvSurvey code, assets, maps or data.

🤖 Generated with Claude Code