gplay tracks (+ availability + testers)

Tracks are where releases live; testers are who may install a closed track. gplay folds the two together because they are operationally coupled (DESIGN §10). Shared conventions (auth, --package, output, exit codes) are in gplay-cli-usage; shipping builds onto tracks is gplay-release-flow.

Inspect tracks

gplay tracks list --package com.example.app          # every track on the app
gplay tracks view --track production                 # one track's full state

tracks view answers "is anything wrong on this track right now?": the latest release, its status, and rollout fraction.

Create a closed track