fix(release): stop shipping native modules built for the wrong runtime

The released installer could not start: it carried a better-sqlite3 build for the
host Node runtime instead of Electron, so the app died immediately with a module
version mismatch when it opened its database.

Packaging now proves the Electron build of every runtime-sensitive native module
before an installer or archive exists, and installers are produced only from that
verified tree, so the mistake cannot pass silently. The release pipelines run the
same check.

The default local model also pointed at a retired model: a *.gguf name that
Ollama cannot serve, while the settings, onboarding, and guide screens
recommended an older model. All of them now use the model the service code
already preferred.

CHANGELOG.md

@@ -13,6 +13,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Cloud-optional backup (encrypted, opt-in)
 - Plugin system for custom pipelines
 
+## [1.3.3] - 2026-09-18
+
+### Fixed
+- **The released installer could not start**: it carried a `better-sqlite3` build for the
+  host Node runtime instead of Electron, so the app failed immediately with a
+  `NODE_MODULE_VERSION` mismatch when opening its database. Packaging now guarantees and
+  verifies the Electron build of every runtime-sensitive native module before an installer
+  or archive is produced, and publishes only from that verified tree.
+- **The local language model default still pointed at a retired model**: the stored default
+  was a `*.gguf` file name that Ollama cannot serve, and the settings, onboarding, and
+  Ollama guide still recommended `gemma2:2b` while the service code already preferred
+  `gemma4:e4b`. All surfaces now default to `gemma4:e4b`.
+
 ## [1.3.2] - 2026-09-18
 
 ### Changed