unity-cli

# Unity CLI One CLI (`cs`) drives the Unity Editor/Player. The default authoring surface is grouped into six agent-facing domains so only the relevant schema enters context; control-plane and project custom commands use explicit views. `cs list-commands` is a control-plane CLI discovery operation, not the canonical package contract `command/list`. Its CLI flags are never `command/list` arguments, and discovery invocations must not be represented as canonical command routes. Only use `command/list` when the user explicitly requests that package contract. The records returned by discovery carry authoring, custom, or control-plane tiers. ## Running `cs` `cs` below means: ```bash python "<SKILL_DIR>/scripts/cli/cs.py" ``` `<SKILL_DIR>` is this skill's absolute base directory, supplied when the skill loads. Expand `cs` to that absolute command on every call and run it without changing directory. Do not enumerate other skill installations or run `cs --help` to rediscover this documented surface; this file and its returned Route Cards are complete for routing. Do not pass `--project` during normal use. The CLI locates the Unity project by walking up from both the working directory and its own committed location. `--project <path>` is only for deliberately targeting a different project. The CLI runs in place; there is no bootstrap or copy step. `cs setup` is a convenience, not a gate. If the package is absent or `--update` is used, setup writes the shared `Packages/manifest.j...