build: four-part releaseVersion (2.0.0.1) injected at packaging time

electron-builder refuses a non-semver package.json version, so the published
number lives in package.json releaseVersion and scripts/dist.mjs passes it as
extraMetadata.version (plus the hotfix digit as Windows build number). The
workflow tags and names the release from the same field.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017Wn5VX9HNbJ7N54hR24u9Y

package.json

@@ -1,6 +1,7 @@
 {
   "name": "eveflow",
-  "version": "2.0.0.1",
+  "version": "2.0.0",
+  "releaseVersion": "2.0.0.1",
   "description": "JARVIS-style desktop HUD for Hermes Agent: voice, streaming runs, scheduled jobs, skills and telemetry",
   "main": "dist-electron/main.js",
   "private": true,
@@ -16,7 +17,7 @@
     "electron": "electron .",
     "start": "npm run build:electron && concurrently -k -s first \"npm run dev\" \"wait-on http://127.0.0.1:5173 && cross-env NODE_ENV=development VITE_DEV_SERVER_URL=http://127.0.0.1:5173 electron .\"",
     "preview": "vite preview",
-    "dist": "npm run build && electron-builder --win --publish never",
+    "dist": "node scripts/dist.mjs",
     "typecheck:electron": "tsc -p tsconfig.electron.json --noEmit"
   },
   "build": {