unityctl-workflowslisted

# unityctl Workflows Use `unityctl` as the execution and evidence layer. Keep source-code edits in normal filesystem tools; use unityctl for Unity-owned state and live Editor operations. ## Establish the target 1. Resolve the Unity project root containing `Assets/`, `Packages/`, and `ProjectSettings/`. 2. Pass `--project` explicitly on every project-scoped command. Discovery commands such as `editor current` and `editor instances` are global and do not accept it. 3. Check the installed CLI and project: ```bash unityctl --version unityctl doctor --project "$P" --json ``` 4. If the bridge is missing, install the bundled bridge, then open Unity and wait for stability: ```bash unityctl init --project "$P" unityctl await-ready --project "$P" --timeout 300 --json ``` Do not run `init` again when `doctor` reports a healthy matching bridge. ## Discover, do not guess Use the live command surface instead of memorizing flags: ```bash unityctl tools --json unityctl <command> --help ``` `tools --json` returns a top-level array. Use names returned by it; the machine command catalog uses hyphenated names while the CLI may expose grouped verbs. ```bash unityctl tools --json | jq '.[].name' ``` ## Run the closed loop 1. Read the current state, including `scene hierarchy --summary`. 2. If any affected scene is already dirty, stop before writing. Ask whether to save the existing work or let the user revert it; do not mix ownership. 3. Compare `editor current --json` with the