chore(release): promote to 1.0.0 stable [version set]

The app is stable, so mark this as the 1.0.0 milestone. The CI bump step
now honors a [version set] marker: when present it ships the pinned semver
as-is and only advances the build number (Play requires it monotonic),
instead of the automatic patch bump that cannot cross the 0.x -> 1.0.0
boundary. Normal commits keep auto-incrementing the patch (1.0.1, 1.0.2, ...).

.gitea/workflows/build.yml

@@ -73,12 +73,21 @@ jobs:
           CURRENT=$(grep '^version:' pubspec.yaml | awk '{print $2}')
           SEMVER=$(echo "$CURRENT" | cut -d'+' -f1)
           BUILD=$(echo "$CURRENT" | cut -d'+' -f2)
-          MAJOR=$(echo "$SEMVER" | cut -d. -f1)
-          MINOR=$(echo "$SEMVER" | cut -d. -f2)
-          PATCH=$(echo "$SEMVER" | cut -d. -f3)
-          NEW_PATCH=$((PATCH + 1))
           NEW_BUILD=$((BUILD + 1))
-          NEW_VERSION="${MAJOR}.${MINOR}.${NEW_PATCH}+${NEW_BUILD}"
+          # If the triggering commit explicitly pins the version name via the
+          # [version set] marker, ship that semver as-is (a milestone like 1.0.0
+          # or a major/minor jump the automatic patch bump cannot reach) and only
+          # advance the build number, which Google Play requires to stay
+          # monotonic. Otherwise keep the default automatic patch+build bump.
+          if git log -1 --pretty=%B | grep -q '\[version set\]'; then
+            NEW_VERSION="${SEMVER}+${NEW_BUILD}"
+          else
+            MAJOR=$(echo "$SEMVER" | cut -d. -f1)
+            MINOR=$(echo "$SEMVER" | cut -d. -f2)
+            PATCH=$(echo "$SEMVER" | cut -d. -f3)
+            NEW_PATCH=$((PATCH + 1))
+            NEW_VERSION="${MAJOR}.${MINOR}.${NEW_PATCH}+${NEW_BUILD}"
+          fi
           sed -i '' "s/^version: .*/version: ${NEW_VERSION}/" pubspec.yaml
           git add pubspec.yaml
           git commit -m "chore: bump version to ${NEW_VERSION} [ci skip]"