Bump shared-actions pins to 18bed1ca

[leynos]

Summary

• Advance every leynos/shared-actions pin to 18bed1ca49a6de3d8882bd72635a32ae3f023d57 (shared-actions main HEAD), in both this repo's own .github/workflows/*.yml and the copier template sources under template/.github/workflows/*.jinja, so newly generated projects start at the same pin.
• Picks up the coverage-ratchet baseline-advance fix and the symmetric ±1pp dead-band (shared-actions#353), plus routine follow-ups (#354, #356 whitaker-installer 0.2.6, #344).

Review walkthrough

• .github/workflows/{ci,act-validation,dependabot-automerge}.yml: repo's own CI pins bumped (previously on three different stale SHAs).
• template/.github/workflows/{ci,act-validation,coverage-main}.yml.jinja: template source pins bumped, keeping templating syntax intact.
• Left tests/test_helpers.py (lines 559/567/724) and tests/helpers/ci_contracts.py untouched: these are synthetic fixtures and shape-only regexes for contract tests, not real pins.
• A repo-wide grep confirms no other 40-hex shared-actions SHA remains outside those fixtures.

Validation

• make test — 47 passed, 2 skipped, 3 snapshots passed.
• CI green on this branch

[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: 44 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: 245e5b07-fd28-41b1-9e5e-8b1983d246df

📥 Commits

Reviewing files that changed from the base of the PR and between bb030cf and 6ad084a.

📒 Files selected for processing (6)

• .github/workflows/act-validation.yml
• .github/workflows/ci.yml
• .github/workflows/dependabot-automerge.yml
• template/.github/workflows/act-validation.yml.jinja
• template/.github/workflows/ci.yml.jinja
• template/.github/workflows/coverage-main.yml.jinja

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-shared-actions-pin

---

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