Release 2.2.37 with cloud sync configured

The published APK carries the Vercel origin and the write-only ingest token.
Verified against the signed artifact: the origin and token are present, and no
MongoDB URI, host or password appears anywhere in the dex.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## 2.2.37
+
+### Added
+
+- Cloud sync is configured. The build carries the API origin and a write-only ingest
+  token, so daily consumption and completed DC charging sessions reach MongoDB, and
+  whatever queued up while offline is uploaded once connectivity returns.
+
+### Changed
+
+- The consumption API moved from a standalone Express service to a Next.js app on Vercel,
+  which also serves a dashboard for reading the history back. The token in this APK opens
+  the write endpoints only — reading needs a password the APK does not contain, and the
+  MongoDB URI remains server-side and has never been in a build.
+
 ## 2.2.36
 
 ### Changed

FatihsMG4-unstable-2.2.37.apk.sha256

@@ -0,0 +1 @@
+2d9fbd26a5afa6b0aaf21519204f825b32b45dd7e7165918c0685669cbd9b9bd  FatihsMG4-unstable-2.2.37.apk

app/build.gradle

@@ -34,8 +34,8 @@ android {
         applicationId "com.evsuite.abrp"
         minSdk 27
         targetSdk 36
-        versionCode 53
-        versionName "2.2.36"
+        versionCode 54
+        versionName "2.2.37"
 
         // MongoDB credentials never ship in the APK. The app only talks to the small
         // authenticated API in server/, which owns the database connection.