Prepared the 1.41.0 release.

[AlexSkrypnyk]

Summary

Prepares the 1.41.0 release by bumping the pinned CI, tooling, and platform version surface, refreshing dependency lockfiles, and re-recording the installer demo video to reflect a Tools multiselect change.

Changes

• Bumped drevops/ci-runner from 26.7.0 to 26.8.0 across 9 references: .circleci/config.yml, .circleci/vortex-test-common.yml, .github/workflows/audit.yml, .github/workflows/build-test-deploy.yml (4 jobs), and .github/workflows/vortex-test-common.yml (2 jobs).
• Bumped the drevops/vortex-tooling pin from 1.3.0/~1.3.0 to 1.4.0/~1.4.0 in the root composer.json require constraint and path-repository versions override, scripts/vortex-tooling.sh, and .vortex/tests/phpunit/Traits/SutTrait.php, and updated the matching doc mention in .vortex/CLAUDE.md.
• Raised the platform PHP version from 8.4.21 to 8.4.23 in composer.json (config.platform.php) and phpstan.neon (phpVersion 80421 -> 80423) to match the container's reported PHP version, and updated the illustrative example in .vortex/docs/content/drupal/composer-json.mdx.
• Bumped drevops/behat-steps to ^3.13.0, mglaman/phpstan-drupal to ^2.1.2, and rector/rector to ^2.6.2 via composer update -W and bump-after-update.
• Refreshed the theme lockfile web/themes/custom/your_site_theme/yarn.lock with in-range updates only.
• Re-recorded the installer demo video assets (installer.json, .svg, .png) to reflect the installer's Tools multiselect gaining Twig CS Fixer and the optional dclint/hadolint entries.

Publish order

drevops/vortex-tooling 1.4.0 does not exist on Packagist yet. CI passes here because the template resolves the package through the in-repo path repository, but a consumer project resolves it from Packagist, where ~1.4.0 currently has nothing to match. Two things therefore depend on that tag being published first:

• Tag and publish drevops/vortex-tooling 1.4.0 before tagging Vortex 1.41.0, per the release process. The tooling changed substantially this cycle (80 files, +3838/-1105), so a new tag is required rather than optional.
• The remaining five demo videos (build, provision, lint, test, test-bdd) cannot be re-recorded until then. They were regenerated during release prep but every recording captured [FAIL] Composer command failed. with found drevops/vortex-tooling[dev-main, 1.0.0, 1.1.0, 1.2.0, 1.3.0, 2.x-dev] but it does not match the constraint, so they were discarded rather than committed. Only the installer video, which does not resolve Composer against Packagist, is included in this PR.

Before / After

┌───────────────────────────┬─────────┬─────────┐
│ Pinned surface            │ Before  │ After   │
├───────────────────────────┼─────────┼─────────┤
│ drevops/ci-runner (image) │ 26.7.0  │ 26.8.0  │
│ drevops/vortex-tooling    │ 1.3.0   │ 1.4.0   │
│ Platform PHP              │ 8.4.21  │ 8.4.23  │
│ phpstan.neon phpVersion   │ 80421   │ 80423   │
│ drevops/behat-steps       │ ^3.12.0 │ ^3.13.0 │
│ mglaman/phpstan-drupal    │ ^2.1.1  │ ^2.1.2  │
│ rector/rector             │ ^2.6.1  │ ^2.6.2  │
└───────────────────────────┴─────────┴─────────┘

[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: 20 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: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ca6c575e-ec5a-4301-a305-b6f5730f15f1

📥 Commits

Reviewing files that changed from the base of the PR and between 44a2acc and eaceb9e.

⛔ Files ignored due to path filters (3)

• .vortex/docs/static/img/installer.png is excluded by !**/*.png
• .vortex/docs/static/img/installer.svg is excluded by !**/*.svg
• web/themes/custom/your_site_theme/yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (12)

• .circleci/config.yml
• .circleci/vortex-test-common.yml
• .github/workflows/audit.yml
• .github/workflows/build-test-deploy.yml
• .github/workflows/vortex-test-common.yml
• .vortex/CLAUDE.md
• .vortex/docs/content/drupal/composer-json.mdx
• .vortex/docs/static/img/installer.json
• .vortex/tests/phpunit/Traits/SutTrait.php
• composer.json
• phpstan.neon
• scripts/vortex-tooling.sh

---

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

[github-actions]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.56% (206/209)

Per-class coverage

Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.70%. Comparing base (44a2acc) to head (eaceb9e).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3016      +/-   ##
==========================================
- Coverage   87.11%   86.70%   -0.42%     
==========================================
  Files         101       94       -7     
  Lines        4912     4753     -159     
  Branches       47        3      -44     
==========================================
- Hits         4279     4121     -158     
+ Misses        633      632       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

📖 Documentation preview for this pull request has been deployed to Netlify:

https://6a7fba444c35c45c42a3797d--vortex-docs.netlify.app

This preview is rebuilt on every commit and is not the production documentation site.