[delete-cloud]

Summary

• create `` before running pip in the Woodpecker lint-and-smoke-tests step
• keep the runner cache PVC mount from ci: use Woodpecker runner pip cache #660 and leave image build steps unchanged

Why

• Woodpecker pipeline Close durable runtime storage and tracing audit #210 confirmed the PVC mounted at /cache, but pip disabled caching because /cache/pip/coding-agent-loop did not exist with ownership acceptable to the root-running step.
• Creating the leaf directory in the step makes the cache usable on an empty or cleaned PVC.

Verification

• git diff --check -- .
• woodpecker-cli lint .woodpecker/ci.yml
• woodpecker-cli lint --strict .woodpecker/ci.yml
• delegate verification: same commands passed
• dispatcher P1/P2 review: one-line follow-up, no code/scope issue found

Rollout notes

• trusted.volumes is already enabled for kina/Coding-Agent-Loop; network/security trust remain false and fork PR approval remains enabled.
• After merge and Forgejo sync, verify the next Woodpecker run does not print the pip cache-disabled warning and that /srv/sre-data/ci/woodpecker-runner-cache/pip/coding-agent-loop is populated.

[coderabbitai]

Warning

Review limit reached

@delete-cloud, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 597b71e4-a557-46c5-8834-ce66a93fc951

📥 Commits

Reviewing files that changed from the base of the PR and between 123d1d6 and f4b6f8f.

📒 Files selected for processing (1)

• .woodpecker/ci.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/woodpecker-pip-cache-dir

---

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