chore: Remove the version field from default-tools.json

[hatayama]

Summary

Part 4 of the version-gate consolidation (G4), following #1501/#1503/#1504. The stamped version in cli/common/tools/default-tools.json had zero gates or guards; its only consumer was the Version field in uloop list output. That display now reads the embedded contract's projectRunnerVersion, which release-please stamps to the same value, so the output is unchanged while one release-please extra-file entry and one value-to-keep-consistent disappear.

• Remove version from default-tools.json and the Version field from ToolCatalog
• uloop list renders clicontract.ProjectRunnerVersion() (same key, same position, same value at release time)
• Drop the corresponding release-please-config.json extra-files entry and update the config test
• Refresh shared-inputs stamps (cli/common/tools/types.go is a shared common input)

Validation

• scripts/check-go-cli.sh, scripts/test-release-please-config.sh, scripts/test-stamp-release-inputs.sh
• check-release-triggers: passed
• uloop list output verified identical before/after

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 16 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: fa8244ab-567f-4e80-bdae-ba22d068aa94

📥 Commits

Reviewing files that changed from the base of the PR and between d2ddbce and e82739d.

📒 Files selected for processing (9)

• .coderabbit.yaml
• cli/common/tools/catalog_test.go
• cli/common/tools/default-tools.json
• cli/common/tools/types.go
• cli/dispatcher/shared-inputs-stamp.json
• cli/project-runner/internal/projectrunner/list_output.go
• cli/project-runner/shared-inputs-stamp.json
• release-please-config.json
• scripts/test-release-please-config.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor/remove-default-tools-version

---

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.}

[cubic-dev-ai]

No issues found across 9 files

_{Re-trigger cubic}