---
name: verify
description: Build and verify PlayableAds Unity HTML and Google ZIP artifacts, inspect failures and report local versus release readiness. Use for PlayableAds export QA and release checklists, not automatic ad uploads or campaign launches.
---

# Verify playable exports

Work in the user's selected PlayableAds checkout, never the plugin cache. Read its `AGENTS.md`, `README.md`, `docs/authoring.md`, `docs/platform-checks.md` and relevant game briefs. Use that checkout's commands and validators. If no project or game can be identified, ask for the missing selection. Do not change project versions, remotes or unrelated files during verification.

## Local preview

Use `npm.cmd` in PowerShell and `npm` elsewhere. For local QA or pending destination details, run `npm run build -- --game <id> --mode preview` and `npm run verify -- --game <id>`. Use `--all` instead of `--game` for all games when requested. Run the checkout's type checks, tooling tests and relevant exported-browser tests. `npm run check` is the complete reference suite; it rebuilds preview outputs and does not establish a new game's coverage unless tests have been added for that game.

Inspect portrait/landscape play, rotation, hidden-state pausing, replay and explicit CTA dispatch through the available host harness. Report tests that could not be run. Validate actual Unity HTML and Google ZIP contents, not merely development pages. Read `dist/<id>/report.json` for mode, artifact paths, byte sizes, hashes and check results. Distinguish intercepted SDK dispatch from navigation blocked in a platform preview and an actually verified destination.

If the checkout supports embedded manifests, read its `docs/export-manifest.md` and use its verifier. Manifests are automatic; on such checkouts, rebuild older exports with missing manifests and fix the source/build cause of integrity or identity failures rather than patching the manifest. Google preview/release artifact hashes differ because their embedded modes differ. The manifest content hash excludes the manifest comment; use the report's full artifact hash for platform evidence. A valid unsigned manifest establishes neither trusted origin nor compliance by itself: retain independent technical checks and pending platform acceptance. Older checkouts may lack manifests; do not silently upgrade them or claim they perform these checks.

## Release intent

If release verification is requested, check the brief against supplied real app/store configuration, target OS and campaign intent. Unknown material details stay **pending**: preview checks can continue but must not be presented as release qualification. Do not fabricate URLs or silently replace release output with preview output; run the full preview suite before the final requested release build.

Use the existing release build and verification commands with the configuration required by the selected platform; Google-only release builds require no Unity store URLs. Unity embeds its configured URL, so a destination change needs a rebuild. Google uses `ExitApi.exit()` and campaign routing; the game does not supply a custom click URL. Follow the project's documentation for deep links and external-website requests instead of adding navigation code.

Keep manual platform/device results tied to exact artifact hashes. Only record results actually observed or explicitly supplied by the user, attributed accordingly. A successful local check, ES5 syntax check or earlier upload does not prove moderation approval, legacy-device compatibility or acceptance of newly rebuilt artifacts. Never upload creatives or start campaigns automatically. Finish with separate local-check results and pending release/platform checks.


## Universal Google exports (toolkit capability check)

Before using platform-selection flags, inspect the selected checkout's README and `tooling/cli.ts` for `--platform google|unity|all` build support and its report schema. An installed plugin update does not upgrade the project. On an older checkout, use its documented commands and explain that universal exports require a reviewed toolkit upgrade; do not silently pull or modify it.

On a compatible checkout, Google builds use `--platform google` without `--os` and produce one `dist/<id>/google/playable.zip`. Google-only release builds do not read Unity store configuration. Keep actual campaign/app/OS/destination checks pending until verified. Unity builds use `--platform unity` with OS-specific URLs; the default `--platform all` retains combined builds. Use `--mode preview` for preview work. `verify --game <id>` validates the entire latest schema-2 report and takes no build-selection flags. A rebuild migrates older reports and removes only the known obsolete per-OS Google ZIPs. Manual Google checks still require `--os` as campaign context, saved as `campaignOs` against the universal ZIP hash.