Implement every task in an approved task set, unattended, and report once at the end.

1. Establish the boundary

Confirm the /unity-cli skill is available in this session's skill listing. If it is not, stop immediately and ask the user to install it; do not proceed with the run by any other means.
Confirm the repository contains Assets/ and ProjectSettings/ProjectVersion.txt. If it does not, stop and report that this skill is Unity-specific.
The user names a task directory, docs/<feature-slug>/tasks/, holding one <NN>-<slug>.md per task. Without one, stop and offer /unity-to-tasks to produce it.
The task set is the approval. Begin on invocation and run unattended until the final report.

2. Work the frontier

Read every task file and its Blocked by edges.

Skip any task whose acceptance criteria are all ticked — that task landed in an earlier run.

Then loop, one task in flight at a time: