For the questions about a place rather than a passage: how hard it
    blows at Groix this afternoon, when the thermal breeze fills in, when
    the mistral eases, whether the models agree, what the swell does at a
    harbour entrance tonight.

    Args:
        lat: latitude in degrees.
        lon: longitude in degrees.
        start: ISO-8601 datetime with the user's UTC offset (e.g.
            "2026-05-01T08:00:00+02:00"). Every time in the answer comes
            back in that offset.
        end: ISO-8601 datetime, timezone-aware.
        models: optional list of model names. Leave it unset for the
            automatic choice: AROME (1.3 km) wherever it reaches the
            window, and the next model that reaches its end when the
            window runs past two days. Name several models (``["arome",
            "icon_eu", "ecmwf", "gfs"]``) only when the user asks whether
            the models agree: each one costs a request.

    Returns hourly ``wind`` per model (speed, direction it comes from,
    gusts, in knots), ``sea`` (wave height, period, direction), and, only
    where they are material, ``current`` (speed in knots, direction it
    flows to, from a tidal atlas where one covers the point) and ``tide``
    (height around mean sea level: read the range and the times of high
    and low water from it, not a depth over chart datum). Each series is
    a table: ``columns`` names the fields once, each of ``rows`` is one
    hour. Also ``openwind_url``, the OhMyWind map centred on the point.

    Answer in a sentence first (the user is often in a car or at the bar),
    then give the few numbers that back it, as a short table or a small
    chart if your interface draws one. No widget comes with this tool:
    the presentation is yours. Offer ``openwind_url`` as "voir sur la
    carte". This is a forecast: never present it as a measurement of
    what is blowing right now.

    Pass a point at sea. Open-Meteo Marine answers from the nearest sea
    cell: a few kilometres inland the ``sea`` values are the open coast's
    (Guipavas, inland of Brest, gets the waves of the rade), further
    inland they come back null, the ``sea`` array present and empty of
    information rather than absent. Wind is always the point's own.

    Note: the first request after inactivity may incur ~5s of cold-start.