vendo firmware staging manifest
===============================

This records what was copied into publish/images/nodemcu/0.3.0.
It is not evidence that a unit was flashed.

artefact          sub-vendo-firmware-0.3.0.vendofw
flasher sources   avifi-nodemcu-flasher-src-0.3.0.zip
staged            2026-09-27T18:22:56Z
firmware version  0.3.0  (read from the signed manifest inside the file)
signed with       provisioning/update-key.pub (the fleet update key)
file mtime        2026-09-27T18:22:41Z
file sha256       c25b77266bd3a4d5915686c1f6579cdf29e47b6b77d010b241c9a46de8b9f017
file size         300633 bytes
git commit        9aef4e9bda8b9c5fe89cc431bd0cc2aa9d5352a7
working tree      clean
board             NodeMCU 1.0 / ESP-12E (PlatformIO board=nodemcuv2)

This is the image a NodeMCU sub vendo runs, packed with an Ed25519
signature the flasher checks before it will write anything. The sha256
above is of the whole signed file; the image inside carries its own,
covered by that signature. Verifying the download against SHA256SUMS
tells you it arrived intact — the flasher's own check is what tells you
it was released.

Put this file in the folder beside SubVendoFlasher.exe. It is not
loaded into the installer at build time and there is no raw .bin to
flash: the installer refuses an unsigned image, which is what makes it
safe to hand an operator the firmware separately.

The Windows flasher sources are a zip of firmware/installer, not
SubVendoFlasher.exe — PyInstaller does not cross-compile, so that .exe
is built on Windows from these sources.