Plan next-version frontend UI polish

[acodebeard]

Context

While preparing the public v1.0 submission, we identified three frontend UI directions that are worth considering for the next version rather than expanding the current release scope.

This is not intended to block v1.0 submission.

Candidate UI directions

1. Trip awareness layer

   • Build on the fixed waypoint status button.
   • Consider a compact expandable itinerary summary so users can confirm what they have already added without losing their place in search results.
   • Preserve the current no-auto-scroll behavior when adding waypoints.

2. Results confidence

   • Improve scanability of result cards.
   • Consider stronger distance hierarchy, clearer selected states, and better loading/empty states.
   • Keep the interface compact and accessible.

3. Showcase polish

   • Improve screenshot-ready states for the public repo and plugin review context.
   • Make route preview, Google Maps handoff, configured copy, and failure/loading examples feel more polished without making the plugin site-specific.

Notes

• Keep the plugin generic and location-agnostic.
• Preserve keyboard access, real buttons, status announcements, and color-mode behavior.
• Avoid adding broad new feature scope until the v1.0 release is submitted.