Data source: Exobiology prediction, sampling distance & POIs (replacing Canonn API) #96

Part of the Phase 1 backlog (#87). Milestone: Phase 5 — Materials & exobiology.

Note on Canonn API: The legacy api.canonn.tech (Strapi REST API) is permanently unmaintained and unreachable. This issue refines the original scope by replacing the external Canonn dependency with reliable, modern sources: an offline deterministic exobiology prediction engine plus EDSM / EDAstro for Points of Interest (POIs).

Revised Data Sources & Architecture

1. Exobiology Species Prediction & Sampling Rules (100% Offline)

Rather than querying an external web service, exobiology prediction is deterministic and can be computed directly from the journal's Scan event data (the approach proven by Observatory BioInsights and ED-BioScan).

• Input parameters from Scan event:
  • Atmosphere and AtmosphereComposition (e.g. Ammonia, Carbon dioxide, Argon, Water, etc.)
  • SurfaceTemperature (K) and SurfaceGravity (G)
  • PlanetClass (Rocky body, High metal content, Icy body)
  • Volcanism and parent StarType
• Output:
  • Candidate species prediction: When a body has bio signals (from FSS or DSS), evaluate which species match the planetary physics.
  • Minimum clone sampling distance: Every genus has a fixed spatial distance required between genetic samples (e.g. Bacterium: 500m, Stratum: 500m, Tubus: 800m, Frutexa: 150m, Tussock: 200m, Clypeus: 150m, Fonticulua: 500m).
  • First Discovery valuation: When WasDiscovered == false, apply the 5× Vista Genomics first discovery bonus multiplier to the baseline value already present in exobiology-species.json.

2. Points of Interest (POIs) & Codex (EDSM & EDAstro)

• EDSM POI API: Extend the existing EliteDangerous.Edsm client with POI query support:
  • System POIs: GET /api-v1/system?systemName={name}&include=poi
  • Nearby / sphere POIs: GET /api-v1/sphere-systems?systemName={name}&radius={ly}&include=poi or /api-v1/poi
  • Retrieves tourist beacons, historical sites, planetary anomalies, and notable stellar phenomena.
• EDAstro Curated Datasets: Static CDN-hosted JSON datasets for:
  • Deep Space Support Array (DSSA) permanent carriers (vital for deep-space explorers seeking repair/cartographics).
  • Guardian ruins & structures.
  • Thargoid surface sites, Titans, and Spire sites.

3. Exobiology Route Planning

• Multi-stop exobiology routing across systems belongs in Data source: Spansh extra routers & finders (RtR, exobio, tourist, body/station/market search) #98 (EliteDangerous.Spansh exobiology router), keeping routing isolated to Spansh.

Sketch / Proposed Changes

1. EDNexus.Core/Exobio:
   • Add genus minimum sample distances and species environmental spawning criteria to ExobiologyCatalog / exobiology-species.json.
   • Update ExobiologyTracker to evaluate Scan events against the criteria, attaching predicted species and sample distances to BodyBioSignals.
2. EliteDangerous.Edsm:
   • Add EdsmPoi models and GetPointsOfInterestAsync(string systemName, ...) to EdsmClient.
3. UI / Dashboard / Overlay:
   • Exobiology card: Show candidate species, predicted payout (with 5x bonus indicator when undiscovered), and required sample distance.
   • In-game overlay: Display min sample distance and top species value for the current body.
   • Voice callouts: Announce high-value candidate species when scanning bodies.

Why this is superior

• Immune to API downtime: Exobiology prediction, sample distances, and payouts work completely offline.
• Zero new external dependencies: Reuses the existing EliteDangerous.Edsm client.
• Immediate gameplay value: Solves the Phase 3 - Colonisation construction tracker #1 question on-foot explorers have: "What can be here, is it worth landing, and how far apart do I need to sample?"