Back to Details

phaser4-game-release

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Phaser 4 发布与合规

Phaser 4 Release and Compliance

全局控制接入

Global Control Access

控制面边界：可提议、可审查、可在已建立且任务授权有效的发布 Work Item 范围内准备，且必须回到 
$phaser4-game-workflow-control
审计和状态迁移；A5/A6 外部、真机与发布操作逐对象请求批准。
发布必须创建独立 Work Item。
phaser-build-upload
、
phaser-backend-config
、
phaser-channel-config
为 A5；
phaser-device-test
、
phaser-store-submit
、
phaser-release
、
phaser-game-rollback
为 A6，先由 
phaser4-game-workflow-control
 校验精确游戏目标和 F4 审批。Git、GitHub Release、消息和通用第三方 API 不属于此生命周期控制面。
准备可提审交付物不等于已经提交或上架。账号、签名密钥、令牌和个人数据只可放在受控外部密钥系统。
读取独立发布 Work Item、平台矩阵、资源登记、测试计划和发布清单。F0 校验授权合规，F1 校验候选与发布规格，F2 完成 QA/技术/合规领域质量，F3 绑定工程证据，F4 只决定记录中明确的外部对象和发布动作。
  1. 分别核对小游戏、iOS、Google Play 的打包、版本、图标截图、描述、隐私、分级、广告或内购披露、数据收集与账号删除要求。
  2. 新渠道先新增独立平台矩阵行，完成适配、资料、合规和测试评审后再纳入候选。
  3. 只从可复现候选 SHA 和实际执行的构建命令生成候选包，使版本、包哈希与测试证据一一对应。共享基础和关键玩法流证据只能证明各自范围；G3/release 必须执行完整渠道/平台矩阵，不得自动发起真机验收。
  4. 涉及 API 或生产服务时核对契约版本、认证授权、幂等/重试/超时、客户端兼容、迁移/回滚、测试、部署监控和备份恢复；服务端不在范围时只核对外部依赖、所有者和客户端边界。
  5. 在平台矩阵和发布清单登记候选包、完成项、阻断项、风险与建议，向总控提交只读 F2 结论；只有总控可写任务 
    review.md
    。F3 不自动合并或发布，未获 G3 明确放行不得声称可以提交或已经上架。
Control Plane Boundary: Proposals, reviews, and preparations can be made within the scope of established and authorized release Work Items, and must return to 
$phaser4-game-workflow-control
for auditing and state migration; A5/A6 external, real-device, and release operations require approval on an object-by-object basis.
A separate Work Item must be created for release. 
phaser-build-upload
, 
phaser-backend-config
, 
phaser-channel-config
are categorized as A5; 
phaser-device-test
, 
phaser-store-submit
, 
phaser-release
, 
phaser-game-rollback
are categorized as A6, which require verification of precise game targets and F4 approval from 
phaser4-game-workflow-control
 first. Git, GitHub Release, messages, and general third-party APIs are not part of this lifecycle control plane.
Preparing deliverables ready for submission does not mean they have been submitted or launched. Accounts, signing keys, tokens, and personal data can only be stored in controlled external key systems.
Read independent release Work Items, platform matrices, resource registrations, test plans, and release checklists. F0 verifies authorization compliance, F1 verifies candidate and release specifications, F2 completes quality checks in QA/technical/compliance areas, F3 binds engineering evidence, and F4 only decides on explicit external objects and release actions recorded.
  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.