ci(release): device gate, diff summary, and staged production rollout

[TimeToBuildBob]

The release-discipline half of the #261 follow-up (the CI half is #264).

What changes for you when releasing

1. Release workflow gets two inputs. installed_on_device (checkbox) must be ticked for a stable version or the job fails with a message saying what to install and check. rollout (default 0.1) is the initial production fraction.
2. The job summary lists every commit and the aw-server-rust submodule range since the previous tag. "Small bump" gets decided by that list, not by feel. (v0.14.0's would have shown 12 PRs and 25 server commits.)
3. Build workflow publishes stable tags to production as a staged rollout: the fraction comes from the tag annotation (rollout=…, written by Release), defaults to 10% for a hand-pushed tag, and refuses unknown values instead of silently going to 100%. Internal track is untouched. Resolver lives in scripts/assert-play-track.sh rollout with self-tests, run by the existing self-test step on every PR.
4. New Rollout workflow (Actions → Rollout → 0.25 / 0.5 / 1.0) widens or completes the current production release via a new fastlane rollout lane (upload_to_play_store with skip_upload_*, version_code defaults to the highest on the production track). Check Play vitals for the new versionCode first; the Blank white screen and app not working #261 ANR clusters were visible within hours.

Pre-releases (0.14.1b1, dev…) are unaffected: internal track, no gate.

Validated: assert-play-track.sh --self-test (7 new cases), workflow YAML parses, ruby -c Fastfile. The upload_to_play_store rollout-update call is fastlane's documented way to change an in-progress staged rollout; first real use will be the v0.14.1 rollout, so worth watching that run.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no actionable new defect or outstanding previous finding remains.

Findings

1.  Prerelease tag hides changes ▶
2.  Tag lookup remains untested ▶

Summary

• Requires real-device confirmation before stable releases.
• Summarizes the complete production release range, including bundled server changes.
• Resolves rollout fractions from annotated tags with fail-closed validation.
• Adds a workflow and Fastlane lane for widening an active production rollout.
• Avoids repeatedly submitting unchanged Play listing media.
• The changes since the previous review fully address both earlier findings by selecting the prior stable tag and exercising the real annotated-tag lookup path.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    Request[Manual release request] --> Gate{Stable release?}
    Gate -->|Yes| Device[Require device validation]
    Gate -->|No| Prepare[Prepare prerelease]
    Device --> Summary[Summarize changes since previous stable tag]
    Prepare --> Summary
    Summary --> Tag[Create annotated release tag]
    Tag --> Build[Build and validate artifacts]
    Build --> Track{Play track}
    Track -->|Internal| Internal[Publish prerelease]
    Track -->|Production| Staged[Start annotated staged rollout]
    Staged --> Vitals[Check Play vitals]
    Vitals --> Rollout[Widen or complete rollout workflow]

Loading

_{Reviews (2) · Last reviewed commit: "fix(ci): baseline stable summaries on pr..."}

[TimeToBuildBob]

@greptileai review

[TimeToBuildBob]

CI-green and mergeable (Greptile 5/5) — waiting only on a maintainer click.

This PR is ready to merge, but the bot has pull-only access to this repo and can't self-merge — surfacing it here so it isn't lost. The monitoring loop will stop re-flagging it now that this note is posted.