Pakua Unity CLI 1.0.0.20010

Highlights of 1.0.0-beta.10 (full notes at the release notes URL):
- Security: unity mcp configure no longer follows a symlinked path component when writing a client's config file, confining a --local write to the project directory and closing an arbitrary-file-overwrite gap a malicious cloned repo could trigger. Every client config write is now atomic.
- Security: unity mcp configure --dry-run no longer prints your whole existing MCP config file, which is exactly where per-server credentials live.
- Security: the resident auth broker now signs every refresh-token request with a DPoP (RFC 9449) proof, and both its signing key and its token store are hardware-backed where the machine supports it: TPM on Windows and Linux, Secure Enclave on macOS.
- Security: the Editor identity daemon and the auth broker now verify a connecting peer's code signature before serving it on macOS and Windows, and on macOS the CLI no longer ad-hoc re-signs a downloaded plugin or component whose signature fails to verify.
- unity context defines named bundles of the five defaults you otherwise set one command at a time: active account, default organization, cloud project, editor and install path.
- unity commands emits the CLI's own command tree as a machine-readable manifest, and unity vcs blame reports who last changed each GameObject and component in a scene or prefab, with commit, author and date.
- Unity Accelerator support: unity config accelerator <host:port> persists an import-cache endpoint that unity run, unity test and other commands reuse instead of retyping it per invocation.
- Build discovery and iteration: unity build gains --create-profile, --list-targets and --list-profiles, and unity build run relaunches the most recent successful build without rebuilding.
- unity watch test re-runs unity test --affected on every project change, and a committed ProjectSettings/UnityCliConfig.json declares unity build and unity test defaults once for a whole repository.
- Fixes include Editor discovery from WSL against an Editor on the Windows host, Editors briefly reported unreachable after a recompile, git misreported as missing on Windows on Arm, and self-update and self-install on Windows when a resident helper holds the binary open.