* Surface newly-added built-in waypoints in the extension popup Track which built-in waypoint ids the user has already seen via a new `knownWaypointIds` array in prefs. On upgrade, seed it from the user's existing groups (and legacy hiddenWaypoints) so anything added to the catalog later — e.g. Bluepy for users on pre-0.1.2 installs — shows up as a dismissable "new waypoints" banner in the popup footer. Also replace the footer Settings button with a dark/light theme toggle; the gear in the header still opens settings. Add a "new" tag in the Waypoints picker and group rows so new built-ins are easy to spot. * Inline atptools wrench icon to unblock extension build The extension imports the shared waypoint icon catalog through the `@aturi` Vite alias, which points at `src/utils/`. Rolldown resolves bare specifiers from the importer's directory upwards, so `lucide-react` was unreachable from there even though it lives in the extension's own `node_modules`. The Next.js app finds it via the parent's `node_modules`, which masked the issue locally. Drop the `lucide-react` import from waypointIcons.tsx and inline the Wrench mark as an SVG component. One less third-party dep on a file that's shared by two builds with two different resolution roots. --------- Co-authored-by: Claude <noreply@anthropic.com>