Auto-publish Release-* builds to the Play internal track

Co-Authored-By: Claude Code <noreply@anthropic.com>

.claude/context/standards.md

@@ -137,8 +137,8 @@ existing split instead.
 `.gitea/workflows/release.yml` (on `Release-*` tags) first checks the tag
 equals `Release-<pubspec version>`, builds the signed `.aab`, attaches it to a
 Gitea release, then uploads it with `r0adkll/upload-google-play` to the
-`internal` track as a **draft** (promote in Play Console, or edit
-`track`/`status` in the workflow). Requires the `PLAY_SERVICE_ACCOUNT_JSON`
+`internal` track with `status: completed`, so it rolls out to internal
+testers automatically (promote to other tracks in Play Console). Requires the `PLAY_SERVICE_ACCOUNT_JSON`
 repo secret (service account with release permissions; the app's first
 release must be uploaded manually). Play rejects a repeated `versionCode`, so
 bump the `+N` in `pubspec.yaml` for every tag - re-tagging the same version

.gitea/workflows/release.yml

@@ -89,9 +89,9 @@ jobs:
         with:
           files: ${{ env.AAB_PATH }}
 
-      - name: Upload to Google Play (internal track, draft)
-        # Stages the build only; promote it in Play Console, or change
-        # `status` to "completed" (and/or `track`) to roll out automatically.
+      - name: Upload to Google Play (internal track, auto-publish)
+        # Rolls the build out to internal testers automatically
+        # (`status: completed`); promote it to other tracks in Play Console.
         # Needs the PLAY_SERVICE_ACCOUNT_JSON repo secret, and the app's
         # first release must already have been uploaded by hand.
         uses: r0adkll/upload-google-play@v1
@@ -101,5 +101,5 @@ jobs:
           releaseFiles: ${{ env.AAB_PATH }}
           releaseName: ${{ env.VERSION }}
           track: internal
-          status: draft
+          status: completed
           whatsNewDirectory: distribution/whatsnew