Global Control Integration
Control plane boundaries: may propose, may review, and may prepare within the scope of the release Work Item of the current user task, and must return to $phaser4-game-workflow-control audit and status transitions; A5/A6 external, real-device, and release operations require approval on a per-object basis.
A release must create a separate Work Item.phaser-build-upload、phaser-backend-config、phaser-channel-config is A5;phaser-device-test、phaser-store-submit、phaser-release、phaser-game-rollback is A6, first by phaser4-game-workflow-control validate the exact game target and F4 approval. Git, GitHub Release, messaging, and general third-party APIs do not belong to this lifecycle control plane.
Preparing submission-ready deliverables does not mean they have been submitted or published. Accounts, signing keys, tokens, and personal data may only be stored in a controlled external key system.
Read the separate release Work Item, platform matrix, asset registry, test plan, and release checklist. F0 validates task scope and process, F1 validates the candidate and release specification, F2 completes QA/technical/compliance domain quality, F3 binds engineering evidence, and F4 only decides on the external objects and release actions explicitly recorded.
- Verify the packaging, versioning, icon and screenshot, description, privacy, rating, advertising or in-app purchase disclosure, data collection, and account deletion requirements for mini games, iOS, and Google Play respectively.
- For a new channel, first add a separate platform matrix row, and after completing adaptation, materials, compliance, and test review, include it in the candidate.
- Generate the candidate package from the reproducible actual candidate and the actually executed build commands, so that the version, candidate files, and test evidence correspond. Candidate SHA and package hash are only optional tracking and are not required to be filled in or matched, and do not block release work item acceptance; digest verification is left until after final manual acceptance. Shared foundation and key gameplay flow evidence can only prove their respective scopes; G3/release must execute the full channel/platform matrix and must not automatically initiate real-device acceptance.
- When APIs or production services are involved, verify contract versions, authentication and authorization, idempotency/retry/timeout, client compatibility, migration/rollback, testing, deployment monitoring, and backup and recovery; when the server side is out of scope, only verify external dependencies, owners, and client boundaries.
- Register the candidate package, completed items, blockers, risks, and recommendations in the platform matrix and release checklist, and submit a read-only F2 conclusion to the global control; only the global control may write task
review.md. F3 does not automatically merge or release, and without explicit G3 clearance, it must not claim that submission is possible or that it has been published.