ci: migrate workflows to tenki

[tenki-staging]

👋 Hey there, reviewer!

Experience the fastest GitHub Actions with Tenki, built for performance and cost efficiency.

What does this PR do?

This pull request was automatically generated by Tenki's Migration Wizard.

Here's what's new once you merge:

• ⚡ Faster Runners: Your workflows now use Tenki's high-performance bare-metal infrastructure ~35% faster than
  default GitHub-hosted runners.
  Learn more about Tenki's instance types →

• 💵 Cheaper Runners: as you now use Tenki's high-performance bare-metal infrastructure and WE manage the costs,
  that means for you: 50% cheaper than default GitHub-hosted runners.
  Learn more about Tenki's pricing →

Any questions ?

- Is this free?
Yes, we give you 1,700 free minutes to try Tenki with no strings attached.
If you add a credit card, you’ll also get $5 in free credits every month, renewed automatically.

- Do I need to complete any other steps to migrate to Tenki?
Nope. Hit Merge, and you are good to go 🎊

- Who's can I contact if I have any other questions?
Reach out at hello@tenki.cloud, we will answer you within 24hrs.

Summary by Sourcery

Update GitHub Actions workflows to run on Tenki staging runners instead of production-sized runners.

CI:

• Switch all CI jobs to use the tenki-staging-standard-small-2c-4g runner type across test, code-quality, license, and docker workflows.
• Normalize minor YAML formatting in workflow definitions.

[tenki-reviewer-staging]

tenki-staging[bot] does not have a Code Reviewer seat assigned. You can manage seats in your settings.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Migrates existing GitHub Actions workflows to use Tenki staging runners by updating runs-on labels and performing minor YAML formatting cleanups across CI workflows for tests, code quality, licensing, and Docker builds.

File-Level Changes

Change	Details	Files
Update all affected workflows to use Tenki staging runner type instead of the previous Tenki production runner.	Change runs-on from tenki-standard-large-plus-16c-32g to tenki-staging-standard-small-2c-4g in test-vm workflow jobs (build, fuzz, python-code-quality). Change runs-on from tenki-standard-large-plus-16c-32g to tenki-staging-standard-small-2c-4g in code-quality workflow jobs (formatting-check, traits-check, clang-tidy). Change runs-on from tenki-standard-large-plus-16c-32g to tenki-staging-standard-small-2c-4g in the license workflow check-license job. Change runs-on from tenki-standard-large-plus-16c-32g to tenki-staging-standard-small-2c-4g in the Docker workflow build job.	.github/workflows/test-vm.yml .github/workflows/code-quality.yml .github/workflows/license.yml .github/workflows/docker.yaml
Normalize YAML formatting and workflow configuration without changing behavior.	Remove blank lines after workflow_dispatch or push triggers to tighten YAML formatting. Tighten spacing in pull_request types array in license workflow from spaced list to compact list. Preserve existing commands in steps while normalizing trailing whitespace and newlines (e.g., make check, license.sh, cache-from).	.github/workflows/test-vm.yml .github/workflows/code-quality.yml .github/workflows/license.yml .github/workflows/docker.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[tenki-reviewer]

tenki-staging[bot] does not have a Code Reviewer seat assigned. You can manage seats in your settings.

[sourcery-ai]

Hey - I've left some high level feedback:

• Several jobs that are CPU-intensive (e.g., fuzz tests, Docker build/test matrix) were downgraded from tenki-standard-large-plus-16c-32g to tenki-staging-standard-small-2c-4g; consider whether these workflows still meet timing/performance expectations on much smaller runners before committing this change broadly.
• There are a number of whitespace-only changes (e.g., unchanged run: make check and cache-from lines, and removed blank lines under on: blocks); reverting these would keep the diff focused strictly on the runner migration and make future history/blame easier to follow.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Several jobs that are CPU-intensive (e.g., fuzz tests, Docker build/test matrix) were downgraded from `tenki-standard-large-plus-16c-32g` to `tenki-staging-standard-small-2c-4g`; consider whether these workflows still meet timing/performance expectations on much smaller runners before committing this change broadly.
- There are a number of whitespace-only changes (e.g., unchanged `run: make check` and `cache-from` lines, and removed blank lines under `on:` blocks); reverting these would keep the diff focused strictly on the runner migration and make future history/blame easier to follow.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}