Skip to content

v0.8 — /plan multi-destination porkchop (re-expand from Mars-only) #312

@chipi

Description

@chipi

Tracks the v0.8 re-expansion of /plan from the Mars-only state we cut for v0.7 (per ADR-076) back to the full twelve-destination set.

Implementation plan: RFC-026.

Summary

v0.7 `/plan` advertised twelve destinations (mercury, venus, mars, vesta, ceres, psyche, jupiter, saturn, uranus, neptune, pluto, bennu) but only Mars produced a real porkchop. We shipped a dropdown that promised twelve options and delivered one. v0.7 reduces the dropdown to Mars only so the surface is honest. v0.8 ships the rest.

v0.8 scope

Landing porkchops (Lambert-grid shape, per ADR-026):

  • Mercury
  • Venus
  • Vesta
  • Ceres
  • Psyche

Flyby porkchops (V∞-vs-Tof shape, per ADR-028 — no LOI ∆v term):

  • Jupiter
  • Saturn
  • Uranus
  • Neptune
  • Pluto
  • Bennu

Data layer

Each destination ships a static `static/data/porkchop/.json` Lambert / flyby grid. Generation uses a TypeScript or Python Lambert solver over JPL DE441 ephemerides.

UI changes

Restore the original `DESTINATION_IDS` array in `src/routes/plan/+page.svelte`. The `FLYBY_ONLY` and `GRAVITY_ASSIST_CAVEAT_DESTINATIONS` constants are still in place as dead code (kept by ADR-076 for exactly this purpose). Single-line restore.

Acceptance

  • All 12 destinations plot a real porkchop with no empty regions for in-bounds dates
  • `/plan?dest=` deep-links work for all 12
  • preflight green; new spec covers "every destination renders without console errors"
  • ADR-076 + RFC-026 + this issue closed at v0.8 ship

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions