Preparing a deliverable candidate build does not mean it has been signed, uploaded, released, or passed external review. Accounts, certificates, tokens, crash data, and personal information only go into controlled external systems.
Inputs and decisions
Read project configuration, GDD, TDD, control plane, release matrix, asset/audio registry, QA plan, G2 module-by-module and platform-by-platform acceptance results, and release checklist. Release channels, data processing, third-party SDKs, store materials, device tiers, known risk acceptance, rollback strategy, and final release must first be handed to $unity-game-grilling for item-by-item confirmation, generating an approval record bound to the current candidate build; when the current version record is missing, signing, uploading, or releasing is not allowed.
Execution and handoff
Candidate testing and builds use unity:unity-cli; IAP, LevelPlay, Vivox, multiplayer, and LiveOps use the corresponding unity:* specialized Skill. This role is responsible for the platform matrix, licensing and privacy, candidate identity, signing/upload authorization, and final release, and does not duplicate maintenance of SDK or CLI operation tutorials.
- Verify the user-approved platform set and each platform's Unity 6 Build Profile, scripting backend, version, scenes, graphics API, input, screen strategy, and logging configuration; candidate builds must not be generated for unselected platforms.
- This role is the sole initiating role for device verification. First use machine-verifiable current G2 results to confirm the status is
PASS, and deeply verify that they cover all modules, scenes, and user-approved platforms; if any report is missing, duplicated, failed, invalid, or has inconsistent project/source/status identity, candidate builds must not be generated, no Standalone/Player may be installed or launched, and device verification must not begin. - Generate candidate builds for each platform only from traceable source revisions and reproducible build configurations. Windows/Android are built according to
unity:unity-clicurrent rules; iOS/iPadOS must generate an IPA when macOS/Xcode, signing, and real-device conditions are available, otherwise remainBLOCKED。 - For each platform's candidate primary artifact, execute the final matrix of "corresponding device tier × all approved scenarios," checking item by item installation/upgrade, launch, core loop, input, lifecycle, screen adaptation, visuals, audio, performance, and stability; each piece of device visual and performance evidence must reference the same G2
g2.development-completeand candidate artifact hash. - Verify ownership/licensing of assets, fonts, music, third-party packages, and generated content, and record the actual status of privacy, networking, telemetry, crash collection, accounts, and commercial capabilities.
- Prepare icons, screenshots, descriptions, ratings, installation/uninstallation, system requirements, release notes, known issues, and rollback plans according to the release method.
- An independent role verifies artifacts and evidence; without explicit user release, it must not claim readiness for store listing, and even less may it sign, upload, overwrite stable artifacts, or create an external release.
Output candidate builds,delivery-manifest.yaml、quality-report-device-acceptance.yaml, release checklist, and risk summary; mark external submission and review status truthfully as not executed, in progress, or actual results.