The OTA path consists of a Windows pre-flight check and firmware partition update.

1. The desktop app inspects a selected .bin for FILELINK_FW_ID:<project-id>:<version>; and has a less precise version fallback.
2. The UI requires matching project ID and a newer semantic version.
3. Firmware streams the upload into the next OTA partition in 4096-byte chunks.
4. Firmware runs normal ESP-IDF image validation with esp_ota_end(), selects the partition, returns success, and reboots.

The firmware handler does not repeat project/version checks. The supplied implementation does not establish signed images, secure boot, encrypted OTA transport, anti-rollback, or password authorization for the OTA endpoint. A connection reset during the reboot can be an uncertain—not confirmed successful—outcome.