feat: Editor menus, windows, and CLI messages now use the name Unity Loop Harness

Draft
HA
3d ago
+270-270

Summary

  • The Unity Editor menus, windows, Project Settings entry, and Editor messages now show the name Unity Loop Harness.
  • uloop messages, the Windows executable file details, skill text, and the menu paths in the docs use the new name too.

User Impact

  • Before: the project had been renamed, but the Editor still showed Window > Unity CLI Loop > ..., window titles and Project Settings still said "Unity CLI Loop", and CLI errors and launch output used the old name.
  • After: everything a user reads says "Unity Loop Harness" (for example Window > Unity Loop Harness > Settings). Commands, package IDs, settings files, and type names are unchanged, so existing projects and scripts keep working.

Changes

  • Unity package (C#, uxml, comments) and its tests and samples: replace the spaced display name "Unity CLI Loop" with "Unity Loop Harness". This includes the five Window menu items, window titles, the Project Settings path, the tool-settings menu path embedded in disabled-tool errors, and the execute-dynamic-code readiness snippet. The Editor matches that snippet after hoisting its literals, so changing the literal text does not break the match, even between an old CLI and a new Editor.
  • CLI (shared modules, dispatcher, project runner, release automation): error messages, launch/readiness output, winres.json file details, the winget package name, and the recovery smoke script, with their tests. Shared release input stamps are refreshed with scripts/stamp-release-inputs.sh.
  • Skill sources updated and the .claude / .agents copies regenerated with uloop skills install.
  • README and package docs: menu paths, window names, and image alt text.
  • Identifiers are not renamed: type names, namespaces, asmdef names, settings file names, the [UnityCliLoop] log prefix, package IDs, the repository name, and Go module paths.

Intentionally left unchanged:

  • All CHANGELOG.md files: release history written by release-please.
  • README / README_ja lines that say the project was formerly called Unity CLI Loop and that the Package Manager listed it under that name up to v3.19.0: these are for readers coming from the old name.
  • The "Unity CLI Loop" keyword in Packages/src/package.json: lets people searching for the old name still find the package.
  • The Build and Test Unity CLI Loop workflow name: not user facing, and existing procedures look runs up by this name.
  • productName in ProjectSettings/ProjectSettings.asset of the development project: changing it would move that project's persistent data paths.
  • Images under Packages/src/Documentation~/images/: the text inside them cannot be edited here.

Verification

  • git grep -n 'Unity CLI Loop' -- . ':!*CHANGELOG.md' lists only the 7 lines above.
  • uloop compile: 0 errors.
  • EditMode uloop run-tests, one class at a time, all passed: CliPinReaderServiceTests, CliPinSynchronizerTests, CompileLifecycleRecoveryCoordinatorTests, DomainReloadRecoveryUseCaseTests, CodeAnalysisPluginImporterTests, JsonRpcResponseFactoryWireShapeCharacterizationTests, MacProcessActivityApiTests, SetupWizardWindowTests, ThirdPartyToolMigrationWizardWindowTests, UnityCliLoopEditorSessionStateRepositoryTests, UnityCliLoopEditorSettingsRecoveryTests, UnityCliLoopProjectSettingsRepositoryTests, UnityCliLoopServerControllerRecoveryTests, UnityCliLoopServerStartupProtectionTests, UnityCliLoopSettingsWindowCliActionTests, UnityCliLoopSettingsWindowRefreshPolicyTests, UnityCliLoopToolRegistryTests, ExecuteDynamicCodeUseCaseTests. PlayMode MouseInputSimulationResponseFactoryTests passed.
  • In the Editor, the five menu items exist under Window/Unity Loop Harness/ (Settings, Recordings, Server, Setup Wizard, Custom Tool Migration) and none remain under the old path.
  • Go: golangci-lint fmt --diff, go vet, and golangci-lint run report 0 issues in all four modules; go test passes except two tests that need to bind Unix sockets or create directories under /tmp, which the local sandbox blocks (CI runs them).
  • scripts/test-smoke-cli-recovery-readiness.sh passed.
  • scripts/sync-tool-docs.sh --check and check-skill-size passed.
  • check-release-triggers --base origin/main --head HEAD passed.