fix: Tool Settings pause-point toggle now gates every pause point command

[hatayama]

Summary

Refs: pause-point rename plan (wave 2) — Tool Settings logical tool name

• Rename the Tool Settings toggle and disabledTools storage key from await-pause-point to pause-point, matching the pause point family it controls.
• Route await-pause-point and pause-point-status through the shared settings key on the Go runner so disabled toggles reject both commands (fixes a pre-existing gap where pause-point-status bypassed the gate).
• Drop the explicit toolName: await-pause-point skill override so uloop-pause-point naturally derives pause-point for skill sync and Show Details.

Test plan

• scripts/check-go-cli.sh
• uloop compile — zero errors/warnings
• EditMode: ToolSettingsUseCaseTests, SkillInstallLayoutTests
• CLI: pause-point in disabledTools rejects both await-pause-point and pause-point-status with TOOL_DISABLED
• Unity Tool Settings UI shows pause-point with skill description (manual)

Made with Cursor

[coderabbitai]

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2b890035-7236-4998-ba3a-56e524bece88

📥 Commits

Reviewing files that changed from the base of the PR and between f1d0a9d and 3d50484.

📒 Files selected for processing (11)

• .agents/skills/uloop-pause-point/SKILL.md
• .claude/skills/uloop-pause-point/SKILL.md
• Assets/Tests/Editor/SkillInstallLayoutTests.cs
• Assets/Tests/Editor/ToolSettingsUseCaseTests.cs
• Packages/src/Editor/Application/UseCases/ToolSettingsUseCase.cs
• Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/SKILL.md
• Packages/src/Editor/Domain/ToolSettingsToolLinkPolicy.cs
• Packages/src/Editor/ToolContracts/UnityCliLoopConstants.cs
• cli/project-runner/internal/projectrunner/native_tool_settings.go
• cli/project-runner/internal/projectrunner/pause_point_wait_test.go
• cli/project-runner/internal/projectrunner/runner_commands.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/pause-point-settings-tool-name

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}