Quick start

1. Open Release Guard

Open Tools > Kiwi Studios > Release Guard. Resolve blockers for the workflow you intend to run after reviewing package, Core, editor, host, target, UI, capture, optional-package, and evidence capabilities.

2. Create the default profile

Create the conservative default profile in a project-owned folder and commit it. Release-risk settings are errors, unavailable evidence does not pass, scene ordering remains review-only, automatic fixes require preview and confirmation, external marketplace fields remain external gates, and no baseline is accepted automatically.

3. Run Project Release

Select the profile and intended target, then review each result by stable rule ID, affected object, evidence, explanation, and corrective action. Use Preview Fixes only for findings explicitly marked safe-fix capable.

4. Add UI evidence

Choose the UI evidence scope required by policy: structural/layout evidence, actual-player screenshots, actual-player geometry, focus/navigation, or accessibility mutations such as text, locale, and theme. A baseline is usable only after its exact screenshot, structure, masks, tolerances, target, player, locale, and theme are reviewed.

5. Audit the package root

Run Publisher Mode against the exact customer package root. A local package-root pass still reports portal, platform, official validator, media, licensing, pricing, reviewer, and policy evidence as missing until those gates are actually bound.

6. Export evidence and add CI

Export machine JSON, reviewer HTML, and SARIF where appropriate. Gate CI with the same committed profile and treat missing reports, stale reports, unsupported required capabilities, incomplete transactions, and undocumented exit codes as failures rather than success.

First successful outcome

A successful selected scope is not automatically a release authorization. Final release eligibility still requires every declared platform and marketplace gate for the exact candidate.