Repository navigation
Conversation
…messages The project was renamed from "Unity CLI Loop" to "Unity Loop Harness", but the Editor still showed the old name under Window, in window titles, in Project Settings, and in logs and error messages. Replace the spaced display name everywhere in the package's C# and uxml, including comments, the tool-settings menu path embedded in disabled-tool errors, and the execute-dynamic-code readiness snippet. The readiness snippet is safe to change because the Editor matches it after literals are hoisted out of the source, so the literal text does not take part in the match. Identifiers (type names, namespaces, asmdef names, settings file names, the [UnityCliLoop] log prefix, package IDs) are unchanged. Tests and samples under Assets are updated to the new messages.
Skill bodies still referred to the old "Unity CLI Loop" name in menu paths and field descriptions. Update the skill sources and regenerate the .claude and .agents copies with uloop skills install.
uloop error messages, launch and readiness output, and the Windows executable file details still used the old "Unity CLI Loop" name. Replace the spaced display name in the dispatcher, the project runner, the shared CLI modules, the winget package name, and the recovery smoke script that matches CLI messages, along with their tests. The execute-dynamic-code readiness probe text changes too; the Editor matches the probe after hoisting literals, so an Editor and CLI from different sides of this change still agree. Shared release inputs changed, so the dispatcher and project runner stamps are refreshed with scripts/stamp-release-inputs.sh.
Menu paths such as Window > Unity CLI Loop > Settings and window names in the README and package docs now match the renamed Editor menus. The notes that mention the former name for readers arriving from it stay as they are.
Contributor
|
Important Review skippedToo many files! This PR contains 164 files, which is 14 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry.
 |
hatayama
marked this pull request as draft
October 25, 2026 13:19
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
uloopmessages, the Windows executable file details, skill text, and the menu paths in the docs use the new name too.User Impact
Window > Unity CLI Loop > ..., window titles and Project Settings still said "Unity CLI Loop", and CLI errors and launch output used the old name.Window > Unity Loop Harness > Settings). Commands, package IDs, settings files, and type names are unchanged, so existing projects and scripts keep working.Changes
Windowmenu 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.winres.jsonfile details, the winget package name, and the recovery smoke script, with their tests. Shared release input stamps are refreshed withscripts/stamp-release-inputs.sh..claude/.agentscopies regenerated withuloop skills install.[UnityCliLoop]log prefix, package IDs, the repository name, and Go module paths.Intentionally left unchanged:
CHANGELOG.mdfiles: release history written by release-please."Unity CLI Loop"keyword inPackages/src/package.json: lets people searching for the old name still find the package.Build and Test Unity CLI Loopworkflow name: not user facing, and existing procedures look runs up by this name.productNameinProjectSettings/ProjectSettings.assetof the development project: changing it would move that project's persistent data paths.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.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.Window/Unity Loop Harness/(Settings, Recordings, Server, Setup Wizard, Custom Tool Migration) and none remain under the old path.golangci-lint fmt --diff,go vet, andgolangci-lint runreport 0 issues in all four modules;go testpasses 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.shpassed.scripts/sync-tool-docs.sh --checkandcheck-skill-sizepassed.check-release-triggers --base origin/main --head HEADpassed.