Cleanup Runner

Open Tools → CoCo Asset Flow → Cleanup Runner for the standard cleanup workflow.

The Runner separates four stages:

1. Select Source
2. Select Profile
3. Review Preview
4. Review Apply result

Select Source

Choose one existing child folder below Assets. The Runner scans every non-folder asset recursively.

Changing Source invalidates the current Preview and disables Apply.

Export an Inventory for AI

With only Source selected, choose Scan / Export for AI to write a fresh asset-inventory.json.

This action:

• does not require a Profile;
• does not build an Apply Plan;
• does not modify Unity assets;
• enables Reveal Inventory, Copy Inventory Path, and Copy Solver Request.

Use it only when an external Agent needs evidence for a Source-specific Profile.

Select a saved Profile

The Runner discovers saved *.cleanup.json files below Assets. You can also select an external absolute JSON file explicitly.

The Runner displays a read-only Profile summary. Use Edit Profile to open the selected file in Profile Editor.

Changing the Profile path or file hash invalidates the current Preview.

Validate and Preview

Choose Validate + Preview. The Runner:

1. scans Source;
2. loads and validates the saved Profile;
3. builds the deterministic Plan;
4. writes Preview JSON artifacts.

The progress overlay and Unity Progress window show the current phase, item count, and asset path. Progress is logical work progress, not an estimated remaining time.

Preview is read-only with respect to Unity assets.

Read the summary

The summary separates:

• total assets;
• path changes;
• name changes;
• setting changes;
• generated assets;
• deletes;
• warnings;
• blockers;
• unsupported outcomes.

Use the Dry Run table to search and filter by asset type, rule, severity, Move, Rename, Settings, Generate, or Delete.

Select one row to inspect:

• original and target paths;
• matched rule;
• naming and directory differences;
• importer, Prefab, or FBX changes;
• generated outputs;
• Material remaps;
• Warning or Blocker codes.

Understand status

Warning

The plan can continue, but the item requires informed review. A high Warning count is not automatically a failure; review Warning groups by code.

Blocker

Apply is disabled. Fix the Profile, Source, or project state and build a new Preview.

Unsupported

The requirement cannot be safely represented or executed by the current Profile contract. Do not bypass it with an unrelated broad rule.

Apply the plan

Apply is available only when:

• validation passed;
• there are zero Blockers;
• Source and Profile still match the Preview;
• the Plan is current;
• the user explicitly confirms its Plan ID.

During Apply, do not close Unity or start a second cleanup.

The Executor performs preflight, backup, Move/Rename, quarantine, supported setting changes, verification, final Delete commit, and report publication.

If Unity detects project changes during the operation, the Runner coalesces refresh work and invalidates old state after the synchronous transaction finishes.

Review results

The Results view reports Applied, Deleted, Failed, Rolled Back, and Unsupported counts, followed by verification checks:

• Source Empty;
• GUID identity;
• references;
• final state;
• idempotency.

Use:

• Open Output Folder to reveal the common output root;
• Reveal Report to open the run artifacts;
• Reveal Canonical Audit when a sidecar exists;
• Copy Diagnostics to copy a bounded summary;
• Preview Again to confirm the current zero-change result.

Known transaction failures are grouped by incident so one large pack does not duplicate the same exception across every result row.