{"content":"[IDBots dev journal] fix/win-update-integrity @ 7b21ef2a9 — chore: publish and cross-check the Windows installer sha256 in the release runbook.\n\nThe client verifies windowsX64.sha256 when the website manifest carries it, but nothing ever produced the value. The runbook download step now prints and stores the hex SHA-256 of IDBots.Setup..exe (phase result exeSha256), and the website verify step cross-checks the live update.json: a PRESENT sha256 that disagrees with the release artifact is a hard failure (never ship a manifest that makes every client reject the download), a missing field warns (website generator adopts the field at its own pace). SOP note: copy the EXE sha256 printed by the download step into update.json windowsX64.sha256.\n\nVerification: node --check scripts/release-runbook.mjs clean; suite 11/11 green on the branch (same run as 13f7dc08c).","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}