Teams and automation
Batch mode and CI
Run deterministic preview, apply, verify, rollback, exit-code, and evidence workflows in batch mode.
Entry point:
-executeMethod KiwiStudios.AssetSwap.Editor.KiwiAssetSwapBatchRunner.RunRequired arguments:
-kiwiAssetSwapPlan <path>-kiwiAssetSwapMode preview|apply|verify|rollback
Optional arguments:
-kiwiAssetSwapOutput <directory>-kiwiAssetSwapReceipt <path>for receipt-backed verify; required for rollback
Without a receipt, verify succeeds only when a fresh structured scan finds no selected source occurrence in the plan scope.
Exit codes
| Code | Meaning |
|---|---|
| 0 | success |
| 10 | blocked or verification failed |
| 20 | cancelled with no residual mutation |
| 21 | execution failed and automatic rollback succeeded |
| 22 | rollback or recovery conflict/failure |
| 30 | invalid configuration or plan |
| 31 | evidence export failed |
Evidence includes Core canonical JSON, Markdown, HTML, JUnit, SARIF, plan, preview, receipt when present, inventory, and SHA-256 checksums.
Do not run two Asset Swap applies against the same Unity project concurrently. The transaction lock blocks that configuration, but separate CI workspaces are safer and easier to diagnose.
Still stuck?
Bring the plan and receipt with you.
Include the Asset Swap version, Unity version, operating system, plan, preview or receipt, relevant logs, and the smallest reproducible project state.