drive: cloud run fef37e36

[kjgbot]

Automated drive work from cloud run fef37e36-3a5d-43f3-afb8-998afe05bdef.

The sandbox cannot open PRs (no remote, no GitHub token), so this was delivered
from a host that can. Verification and adversarial review ran in-run — see
ops/reviews/ in the diff. A human merges.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: 5020b001-9e5a-4826-83c8-3afca875d410

📥 Commits

Reviewing files that changed from the base of the PR and between 066ef24 and 98e8e7f.

⛔ Files ignored due to path filters (1)

• sdk/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (8)

• .github/workflows/review-swarm.yml
• .github/workflows/scripts/swarm-post.sh
• .github/workflows/scripts/swarm-prepare.sh
• .github/workflows/scripts/swarm-verdict.sh
• .gitignore
• README.md
• ops/NEXT.md
• workflows/review-swarm.yaml

💤 Files with no reviewable changes (1)

• .gitignore

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR adds a GitHub Actions workflow for non-draft pull-request review swarms. It stages pull-request data, launches and polls a cloud swarm, evaluates fresh lens transcripts, posts evidence comments, and fails unless all reviews pass.

Changes

Cloud review swarm

Layer / File(s)	Summary
Trusted staging and verdict evaluation .github/workflows/review-swarm.yml, .github/workflows/scripts/swarm-prepare.sh, .github/workflows/scripts/swarm-verdict.sh, .gitignore	The workflow checks out immutable gate files. Preparation stages pull-request artifacts. Shared verdict logic selects transcripts and fails closed for missing or unclear results.
Swarm launch and lifecycle .github/workflows/review-swarm.yml, workflows/review-swarm.yaml	The workflow validates RELAY_WORKSPACE_KEY, launches the cloud swarm, polls its status, posts evidence, and fails for non-completed runs.
Staged review and evidence aggregation workflows/review-swarm.yaml, .github/workflows/scripts/swarm-post.sh	Review lenses read staged pull-request files. Aggregation uses swarm_evaluate. Post-processing checks transcript freshness and upserts lens and summary comments.
Setup and delivery requirements README.md, ops/NEXT.md	Documentation defines workspace-secret setup. The operational plan records review-swarm requirements and validation checks.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant CloudSwarm
  participant ReviewWorkflow
  participant VerdictScript
  participant GitHubPR
  GitHubActions->>ReviewWorkflow: prepare staged PR artifacts
  GitHubActions->>CloudSwarm: launch review swarm
  CloudSwarm-->>GitHubActions: return run ID and status
  GitHubActions->>ReviewWorkflow: run review lenses and persist transcripts
  ReviewWorkflow->>VerdictScript: evaluate lens transcripts
  GitHubActions->>GitHubPR: post review evidence and summary comments

Loading

Poem

A rabbit checks the staged review trail
Three lenses pass beneath the cloud veil
Fresh transcripts hop into place
Comments bloom with verdicts and grace
The workflow thumps its paws: success!

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

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

[kjgbot]

Superseded by #164, which is the most complete version of the same review-swarm work (it also adds workflows/review-swarm.yaml, which this one lacks).

These four drive PRs (#161, #162, #164, #165) came from separate cloud runs and three of them re-attempt the same change. Merging more than one would duplicate the workflow and its scripts. Consolidating on #164; closing this rather than leaving three near-identical PRs open.

No work is lost — #164 is a superset. If something here is not in #164, say so and I will port it.