v0.1.51 - Windows update data preservation

Fix Windows updates that rolled back after database count validation.

• Skip byte-identical verified schema and migration files instead of replaying historical cleanup against an existing native database.
• Check every database table before restarting the application. Keep durable record and image preservation checks after startup, while allowing normal completion of temporary direction work and expiration of authentication state.
• Keep failed before/after counts and affected table names through automatic rollback, so a further failure can be diagnosed from the support report.

The correction passed native Windows regression checks, populated PostgreSQL reproduction, isolated actual Windows service update/rollback/reinstall and UI-update tests. The Windows installer and package are verified separately; exact acceptance on the affected Windows 10 VM remains an operator check.

For an existing Windows installation, keep your database and run this release's graphical Setup, choosing Update ALPR already installed on this computer. Verify 0.1.51 under Settings → Release after Finish. Existing passwords, API keys, records, images and settings are retained with a recovery backup. Windows installations with the updater service can then use Settings → Software Updates for later releases.