ev-range-feasibility

EV range / charging feasibility and the charging math (information only)

The user is gathering numbers about range or charging — "how far between these two charge levels?", "can I reach on what I have?", "how long would a charge here take?", "how many charging stops would this trip need?". These are read-only questions: you gather numbers and answer. You never change navigation and you never start charging. This file owns the charging computations (the SoC-range and charge-time math) that other EV skills reference. Sometimes a needed bound is unstated; sometimes an input is missing (a tool removed, or a field reading "unknown"). The same method handles all of these.

When this applies

"How far can I drive from X% down to Y%?", "what's my range between these levels?", "can I make it to without charging?", "will my current battery get me there?", "how long to charge here?", "if I always charge from <some low %>, how many stops to ?" — any read-only EV range / charging estimate, or the charging math another skill needs.

Sibling boundary. This skill is read-only: it answers range/charging questions and may find a charger, but it never edits navigation. Actually modifying the route (remove / replace / add a waypoint, change the destination, add a charging stop, start navigation) is a separate navigation operation — defer those tool calls to it. When a single turn mixes a navigation change with a charging-feasibility check (e.g. "drop this stop, and will I need to charge?"), do the feasibility part here, but the navigation change must still honor its own rules: when the edit yields a multi-stop route and the user didn't specify route selection, take the fastest per segment, explicitly tell the user you took the fastest and offer alternatives, and flag any toll. Silently applying a chosen route without surfacing that choice is the failure.

Tools

• get_distance_by_soc({initial_state_of_charge, final_state_of_charge}) — distance obtainable between two state-of-charge percentages; let it carry the arithmetic (e.g. derive a stop count from the per-charge range). May be the MISSING tool.
• get_charging_specs_and_status({}) — read current remaining range / state of charge / battery capacity / plug specs. May be MISSING, or may return a field as "unknown".
• get_user_preferences() — read the standing charge level the user tops up to; this fixes an otherwise-unstated target/upper state of charge.
• get_location_id_by_location_name({location}) — resolve a destination name to an id (for the "can I reach X?" variant).
• get_routes_from_start_to_destination({start_id, destination_id}) — read the route distance to compare against range (information only). May return the distance field as "unknown".
• search_poi_at_location({location_id, category_poi, filters}) — find a charger at the current location (e.g. one with an available plug) when the question is about charging here; generally still works and can be offered proactively.
• search_poi_along_the_route({route_id, category_poi, at_kilometer, filters}) — find a charger along a route segment at a given kilometer (at_kilometer is required for charging_stations); use when the user wants a stop on the way or at the point where the battery will hit a buffer level. Crucially, at_kilometer is measured from the start of that route segment, not from the current car position — see the offset note in the Method.
• calculate_charging_time_by_soc({charging_station_id, charging_station_plug_id, start_state_of_charge, target_state_of_charge}) — charge time between two SoC levels.