docs: record current Windows installer

.project-docs/30-worklog/tasks/20260824-pi-release-proof-3e725ac7.md

@@ -126,6 +126,28 @@
 
 ## Verification
 
+- At the user's request, Windows x64 was rebuilt from clean task HEAD
+  `2e1b90b7707aa912c576e042b94823dcb183e162` with the exact pinned pnpm
+  `10.33.4` via `pnpm run package:win`. The resulting local NSIS installer is
+  `release/Makelore-2.0.0-win-x64.exe`, 208,525,129 bytes, SHA-256
+  `316FC05C0DC5DA206FA9BE9AA694BEC6DE9DBB2DFBEEEBCFB67472C7F78AF5A3`.
+  Its blockmap SHA-256 is
+  `9E6259C90B41F24A0960EC147A50D5FF2527245669CF7BB98665ADF15D420AA9`;
+  its final `app.asar` remains byte-identical to the reviewed code candidate at
+  SHA-256
+  `872E8D1E7F22994EFF10353DF380016A198C59C145EBF63491E13DA1B1071B7F`.
+  The local installer has no Authenticode signature and may therefore trigger
+  Windows publisher/SmartScreen warnings; no signed-release claim is made.
+- The rebuilt package passed `verify:publish-runtime`,
+  `verify:artifact:win`, `verify:artifact:pi`, `smoke:pi:real`, and
+  `perf:pi:release`. The three structured reports are
+  `release/evidence/pi-artifact-win-2e1b90b.json`,
+  `release/evidence/pi-smoke-win-2e1b90b.json`, and
+  `release/evidence/pi-performance-win-2e1b90b.json`; smoke and performance
+  both record the clean `2e1b90b` commit. Five-sample performance passed all
+  budgets with cold/warm Provider-first p95 `136/134 ms`, 4+4 pressure UI p95
+  `108 ms`, and exit p95 `18 ms`. The packaged fault-injection run retried the
+  same cleanup handle and returned every process and resource counter to zero.
 - Exact pnpm `10.33.4` frozen install passed on Windows and WSL2 Ubuntu 24.04
   x64; both final-product runs were bound to clean commit `09841c8`. The
   lockfile change remains limited to the direct `@electron/asar@3.4.1`