[webdjoe]

TurboBlaze set_mode_from_recipe always set the local status to COOKING. A program with preheat runs the preheat phase first, so it now sets HEATING when the recipe has a preheat time. The DC601S capture reports heating with preheatSetTime/preheatLastTime while a preheat runs.

CS158 and TF101S now send readyStart false, like TurboBlaze, so a cook starts without the device's start button. The CS158 captures show readyStart false reporting cooking/heating at once. TF101S has no capture with readyStart false; its local status after start is now COOKING instead of READY, inferred from CS158.

From PR #560. The pullOut half of that PR was already fixed in 8cbc6f4.

Description

Type of change

• Bug fix (fix:)
• New feature or device support (feat:)
• Documentation (docs:)
• Refactor / test / chore (no functional change)

Checklist

• This PR is a single feature, fix, or edit (not a bundle of unrelated changes).
• The change follows the intended architecture (base class → device + API mixin → device map; state in DeviceState; models in models/; constants in pyvesync.const).
• No API request/response fields were invented — all come from a real packet capture.
• ruff check, pylint, mypy, and pytest pass locally.
• Tests added/updated and API fixtures written (pytest --write_api) where relevant.
• Documentation updated if behavior or public API changed.