ops(next): point the autonomous tick at the CI coverage gap

[kjgbot]

The autonomous cloud tick (workflows/drive-cloud.yaml) reads ops/NEXT.md to choose its work package. That file described building sdk/src/worker.ts as a new file — but it exists and gate-2 workloads run against it. Every overnight tick would assess against a finished package and burn its cycle.

Repointed at the gap that made today expensive: .github/workflows/cloud-runtime-artifact.yml is the only workflow, its one cargo invocation is cargo build (never cargo test), and vitest runs four of ~26 files. Six of eight independent signoffs today found P0s in green PRs — all kernel-side, invisible to CI by construction, including an exactly-once double-fire and a $ref cycle that aborted the daemon and re-ran the effect on every resume.

Scoped to .github/ only, and explicit that a newly-red CI is the correct outcome rather than something to fix or paper over.

ops-only change; no product code.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FtQSAcGDta5VH9xiZFT4sR

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: 3256180e-aab3-4518-89ee-da8b0d892aba

📥 Commits

Reviewing files that changed from the base of the PR and between f16b133 and 468bfd7.

📒 Files selected for processing (1)

• ops/NEXT.md

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

---

📝 Walkthrough

Walkthrough

ops/NEXT.md replaces the SDK worker implementation task with a .github/-only CI coverage task. The task adds kernel workspace and full SDK test execution requirements, preserves existing checks, and specifies evidence and completion requirements.

Changes

CI Coverage Planning

Layer / File(s)	Summary
CI test coverage plan ops/NEXT.md	The work package now requires kernel workspace tests through ops/cargo.sh and the full SDK test script. It retains existing build, verification, and smoke steps. It adds scope constraints, failure handling, local evidence, live-kernel collection requirements, and final repository status capture.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

A rabbit checks the test-run trail
Through kernels hopping without fail
The SDK suite joins the race
Old worker plans yield their place
Fresh evidence fills the pail

---

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