Phaser 4 Release and Compliance

Global Control Access

$phaser4-game-workflow-control

phaser-build-upload

phaser-backend-config

phaser-channel-config

phaser-device-test

phaser-store-submit

phaser-release

phaser-game-rollback

phaser4-game-workflow-control

1. Verify packaging, versions, icons/screenshots, descriptions, privacy settings, ratings, advertising or in-app purchase disclosures, data collection, and account deletion requirements for mini-games, iOS, and Google Play respectively.
2. For new channels, first add an independent row in the platform matrix, and include it in candidates only after completing adaptation, material preparation, compliance, and test reviews.
3. Generate candidate packages only from reproducible candidate SHAs and actually executed build commands, so that versions, package hashes, and test evidence correspond one-to-one. Shared basic and core gameplay flow evidence can only prove their respective scopes; G3/release must execute the complete channel/platform matrix, and real-device acceptance cannot be initiated automatically.
4. When involving APIs or production services, verify contract versions, authentication and authorization, idempotency/retry/timeout, client compatibility, migration/rollback, testing, deployment monitoring, and backup recovery; when the server is not within scope, only verify external dependencies, owners, and client boundaries.
5. Register candidate packages, completed items, blocking items, risks, and suggestions in the platform matrix and release checklist, and submit a read-only F2 conclusion to the master control; only the master control can write to the task

   review.md

   . F3 does not automatically merge or release, and no claim of readiness for submission or launch can be made without explicit approval from G3.