chore: update dispatcher pin to the 3.0.0 stable release

[hatayama]

Summary

• Fresh CLI installs now resolve the 3.0.0 stable dispatcher instead of a stale beta.

User Impact

• Before: install.sh and Unity's Install CLI button follow the pin on main, which still recorded dispatcher-v3.0.0-beta.31 — a fresh install today lands on the beta and its self-update keeps following the beta channel, never reaching 3.0.0.
• After: fresh installs resolve dispatcher-v3.0.0 with its verified asset digests.

Changes

• Stamped the pin with stamp-dispatcher-pin --tag dispatcher-v3.0.0 (release tag + attested digest manifest).
• Packages/src/project-runner-pin.json and .uloop/project-runner-pin.json kept byte-identical.
• minimumDispatcherVersion intentionally left at 3.0.0-beta.31: the package does not require a newer dispatcher, and raising it would lock out working beta CLIs.

Verification

• stamp-dispatcher-pin verified the published release attestations while stamping.
• check-dispatcher-pin passes locally; CI runs the full pin verification against the diff.

https://claude.ai/code/session_01XbhSMKK4LFud57iAmowDz7

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a26e28b9-88fe-4679-96de-45b01fbdd93b

📥 Commits

Reviewing files that changed from the base of the PR and between 36798c2 and 13e202d.

📒 Files selected for processing (2)

• .uloop/project-runner-pin.json
• Packages/src/project-runner-pin.json

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

---

📝 Walkthrough

Walkthrough

Both project runner pin manifests now reference dispatcher release v3.0.0 and its archive checksums. The minimum dispatcher version remains 3.0.0-beta.31 in .uloop/project-runner-pin.json.

Changes

Dispatcher release pin

Layer / File(s)	Summary
Update dispatcher release pins .uloop/project-runner-pin.json, Packages/src/project-runner-pin.json	The archive manifests now contain the dispatcher-v3.0.0 artifacts and SHA-256 checksums. The release tag changed from dispatcher-v3.0.0-beta.31 to dispatcher-v3.0.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 13e20

This updates the dispatcher pin used by fresh installs to the stable 3.0.0 release without any identified merge-blocking risk; it is merge-ready after normal checks and review.

Possibly related PRs

• hatayama/unity-cli-loop#1859: Updates dispatcher pin manifests with release tags and archive checksums.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the dispatcher pin to the stable 3.0.0 release.
Description check	✅ Passed	The description directly explains the dispatcher pin update, user impact, changed files, compatibility decision, and verification steps.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/hatayama/stamp-dispatcher-pin-3.0.0

---

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