#########################
 Alamo Slim HTTP gateway
#########################

``driver/alamo`` defines a raw ``Client`` contract and an ``HTTPClient``
for the Slim gateway. The client uses ``GET /status`` for all
thermostats and ``GET /acao?mac=...`` for one thermostat. An action
changes power or target temperature, not both at once. Its response is
the complete readback for the requested MAC. The caller owns the HTTP
transport.

The address is an HTTP origin without a path, credentials, query, or
fragment. Redirects are rejected. Each exchange has a five-second
caller-derived timeout and a 64 KiB response limit. Records require all
seven documented properties. Extra gateway properties are permitted.
Errors omit request addresses, queries, and response bodies.

Configure thermostats through the manufacturer's application before use.
The gateway exposes local heating activity, not independent load-current
or contactor feedback. Fake HTTP tests do not verify a physical gateway,
thermostat firmware, or electrical safety.

The driver request scheduler applies one minimum six-second
request-start interval to status polls and actions together. Its
operation timeout starts after the rate wait. Caller cancellation or a
command deadline stops the wait without another exchange. A multi-step
command can expire between actions. The gateway budget belongs to one
driver owner.

The private control value uses ``settings.mode`` (``off`` or ``heat``),
``settings.target_temperature`` in degrees Celsius,
``current_temperature``, ``floor_temperature``, ``action`` (``off``,
``idle``, or ``heating``), and ``locked``. Commands contain the complete
mode and target settings only. House-specific target bounds and steps
belong to core validation. The driver accepts finite targets.