fix(ci): enable KVM for Scrapling candidate smoke

[ytallo]

What changed

• enable access to /dev/kvm before validating the Scrapling candidate
• keep the KVM preparation scoped to Scrapling
• add a structural test for the runner preparation contract

Why

scrapling@0.2.7 publishes successfully but cannot complete candidate validation because its sandbox VM cannot access KVM on the hosted runner. The repository already applies the same KVM permission setup for sandbox E2E scenarios.

Impact

Scrapling candidates can boot their sandbox during validation while candidate checks for other workers remain unchanged.

Validation

• 175 passed across .github/scripts/tests
• parsed candidate-smoke.yml with PyYAML
• git diff --check

Classification: no-ticket (CI-only release recovery).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
workers	Ready	Preview	Aug 12, 2026 2:52pm
workers-tech-spec	Ready	Preview	Aug 12, 2026 2:52pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 709dc787-41c6-422c-b3d9-b44ef4b43910

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[github-actions]

skill-check — worker

0 verified, 57 skipped (no docs/).

Layer	Result
structure	✓
vale	✓
ai	✓
render	✓

Four for four. Nicely done.