chore: Merge main into the hot reload integration branch

[hatayama]

Summary

• Merges main into the hot reload integration branch with a merge commit. The integration branch picks up the three changes that landed on main since the last sync.
• The merge commit's first parent is feature/hot-reload-unity-object-support and its second is main.
• No conflicts. The changes are release metadata and the dispatcher pin guard in release automation. No hot reload source changes.

Commits brought in from main

• chore(main): release 3.7.0 #2775: release 3.7.0 (package manifest, changelog, package.json, pin, CLI contract)
• chore(main): release uloop-project-runner 3.5.0 #2776: release uloop-project-runner 3.5.0 (changelog, pin)
• chore: The dispatcher pin guard now requires the Linux dispatcher archive #2936: the dispatcher pin guard now requires the Linux dispatcher archive

Release version fields are taken from main as they are. None were edited by hand.

Merge method

This PR exists to keep a merge commit, so it should not be squashed. Which merge method to use is decided when it is merged.

Verification

• uloop compile: 0 errors.
• go run ./cmd/sync-tool-docs --check in cli/release-automation: the catalog matches the skill parameter tables.
• go test ./internal/automation/... in cli/release-automation: passed. This covers the pin guard change from chore: The dispatcher pin guard now requires the Linux dispatcher archive #2936.
• Unity tests were not run: no hot reload C# source changed in this merge.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: hatayama/unity-cli-loop/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 72f84a43-1cfa-472d-bf8e-e27d548d48da

📥 Commits

Reviewing files that changed from the base of the PR and between f99f1b4 and bf33049.

📒 Files selected for processing (10)

• .release-please-manifest.json
• .uloop/project-runner-pin.json
• Packages/src/CHANGELOG.md
• Packages/src/package.json
• Packages/src/project-runner-pin.json
• cli/common/clicontract/contract.json
• cli/project-runner/CHANGELOG.md
• cli/release-automation/internal/automation/dispatcher_pin_guard.go
• cli/release-automation/internal/automation/dispatcher_pin_guard_test.go
• cli/release-automation/internal/automation/dispatcher_pin_push_test.go

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

Release metadata advances Packages/src to 3.7.0 and project-runner to 3.5.0. Dispatcher pin validation now requires the Linux amd64 archive, with related test fixtures updated.

Changes

Release and dispatcher pin updates

Layer / File(s)	Summary
Release versions and changelogs .release-please-manifest.json, Packages/src/package.json, .uloop/project-runner-pin.json, Packages/src/project-runner-pin.json, cli/common/clicontract/contract.json, Packages/src/CHANGELOG.md, cli/project-runner/CHANGELOG.md	Release metadata advances Packages/src to 3.7.0 and project-runner to 3.5.0. The changelogs add entries for those releases.
Linux archive in dispatcher pin validation cli/release-automation/internal/automation/dispatcher_pin_guard.go, cli/release-automation/internal/automation/dispatcher_pin_guard_test.go, cli/release-automation/internal/automation/dispatcher_pin_push_test.go	Dispatcher pin validation requires the Linux amd64 archive. Tests update the pin fixtures and verify that a manifest without the archive is rejected.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to bf330

The release metadata and dispatcher pin checks show no actionable merge-blocking issue; normal checks remain appropriate.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 12.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 3 files. (7 skipped: 7…	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states that the pull request merges main into the hot reload integration branch. This matches the primary change.
Description check	✅ Passed	The description explains the merge purpose, included changes, verification results, and merge requirements. It is directly related to the changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 12.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 3 files. (7 skipped: 7 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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