Install Whitaker from the released installer in generated CI

[leynos]

Summary

This branch aligns the template's generated CI with the estate-standard Whitaker installation pattern used in leynos/netsuke#410 and the tier 1–2 rollout. The generated workflow previously built whitaker-installer from a pinned git revision; it now installs the released 0.2.5 crate via cargo binstall, keeping the --cranelift flag because generated projects use the Cranelift debug backend. Projects rendered from this template therefore pick up the maintained release channel instead of a fixed commit.

Review walkthrough

• Start with template/.github/workflows/ci.yml: the WHITAKER_INSTALLER_REV environment variable becomes WHITAKER_INSTALLER_VERSION: '0.2.5', the cache key moves to whitaker-v3-… so stale rev-keyed caches are ignored, and the install step uses the guarded cargo binstall.
• tests/helpers/tooling_contracts/workflows.py updates the contract assertion to the new installation log line.
• tests/test_template/snapshots/test_snapshots.ambr is the regenerated syrupy snapshot of the rendered workflow.

Validation

• make test (render, compilation, lint-target, contract, and snapshot suites): 50 passed, 1 xfailed.
• WITH_ACT=1 make test (act-validation suite against a Podman socket, act v0.2.80): 50 passed, 1 xfailed.

Notes

The template's lint target and Makefile Whitaker resolution are unchanged; only the installation channel in the generated CI moves to the released crate.

[sourcery-ai]

Sorry @leynos, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 58 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d80b2ead-7ee2-4261-b551-993ffbfd995b

📥 Commits

Reviewing files that changed from the base of the PR and between 7d7eb00 and fac2539.

📒 Files selected for processing (3)

• template/.github/workflows/ci.yml
• tests/helpers/tooling_contracts/workflows.py
• tests/test_template/__snapshots__/test_snapshots.ambr

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch adopt-whitaker

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ad1c75a5e3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".