[TharunBabu-05]

What changed for users

mqtt status printed MQTT: not connected while a TLS connection was being
set up, directly above the status text TLS handshake with <broker>....
It now prints MQTT: TLS handshake.

It shows when the connection was started from the MQTT app, or by
mqtt connect -r while it retries (every retry goes through the handshake
again).

The change

state_name() in ports/common/td_proto_cmds.c had no case for
TD_MQTT_TLS_HANDSHAKE, so it fell through to default. The switch now lists
every td_mqtt_state_t value and has no default, so -Wswitch (part of
-Wall; the builds use -Werror) reports a state added later. No API change.

Tested

• Host build on Windows (MinGW GCC 15.2), with and without MQTT over TLS
  (mbedTLS v3.6.7, as in CI): no warnings, all 7 CTest programs pass.
• tdsim against a local TCP listener that accepts and never answers, so the
  client stays in the handshake: mqtt connect -r mqtts://127.0.0.1:18883,
  then mqtt status after the first retry.
  • before: MQTT: not connected
  • after: MQTT: TLS handshake
• mqtt status with no connection still prints MQTT: not connected. The CI
  smoke tests (echo through the shell; mqtts reaches "Connecting to") pass.
• With one case removed, the build fails with
  enumeration value 'TD_MQTT_TLS_HANDSHAKE' not handled in switch.
• Not built here: the ESP32 firmware (no ESP-IDF on this machine). The file
  is plain C; CI builds all three boards.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[schikani]

Thanks, real bug and a clean fix. Builds and tests pass here on MinGW too. Merging.