feat(sdk): prepare pinned Babysitter catalog export - #550
Merged
Merged
Conversation
Session-Id: 01a0c82b-2431-7510-9d21-2babb4d23a07
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 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. Comment |
Session-Id: 01a0c82b-2431-7510-9d21-2babb4d23a07
AgentRelayBot
marked this pull request as ready for review
September 22, 2026 08:45
Contributor
Author
|
CLI follow-up is complete at b74fb5b. Marked ready for review for publication-prep scope only. No native artifact was published and activation is not enabled. Focused CLI evidence is in evidence/babysitter-catalog-export/cli-regression.txt. |
kjgbot
pushed a commit
that referenced
this pull request
Sep 22, 2026
Add extensions/babysitter, a schema-2 extension on software-factory whose
eleven GitHub handlers turn Cloud's normalized delivery descriptor into one
cloud:babysitter-turn queue call:
f.capabilities.cloud.babysitterTurn.queue({ delivery }). It sends no
findings, head, label, session, lineage, or config. Unknown input, receipts
other than queued|duplicate, rejections, and a missing capability fail the
run. The manifest matches the #550 exporter permission shape.
#549's refusal is unchanged: hosted execution still refuses the handler
with plugin_unsupported. compat requires the surface release after 2.0.25.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Session-Id: 7d116c0d-6756-4905-ace7-1235559066ed
Co-authored-by: agentrelaybot <agentrelaybot@agentrelay.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloud #3940 must not enable Babysitter from the legacy Claude/comment extension or mutable references. This adds a read-only exporter that fetches an immutable AgentWorkforce/flows ref through the existing SDK, verifies independently supplied bundle and manifest digests, and requires the native Codex/cloud:babysitter-turn permission declaration. It preserves digest-bound manifest bytes, never executes handler code, and refuses to overwrite an output file.
The handoff document identifies the existing Software Factory catalog JSON/API and Cloud parser. This PR does not publish an artifact, change catalog entries, or enable execution. Native handler implementation, reviewed artifact pins, catalog provenance, and released lineage/native-delivery/receipt dependencies remain blockers. #549 intentionally refuses matched handlers; changing permission strings on the old handler cannot close that gap.
Validation used the repository CI local-Surface override (
npm ci --prefix packages/surface --ignore-scripts, thennpm install ./packages/surface --prefix packages/sdk --no-save --ignore-scripts). Initial installed dependencies lacked current Surface hooks/events and relay-helpers rampClient; refreshing/building the local dependencies resolved those setup failures. No dependency manifests or gates changed.Captured verification (also committed at evidence/babysitter-catalog-export/verification.txt):
CLI regression follow-up: invokes the real command with offline GitHub responses and covers successful export, EEXIST with byte preservation, and digest refusal without output creation.
Note
Low Risk
Adds offline export/validation tooling and docs only; it does not change catalog data, Cloud enablement, or extension execution paths.
Overview
Adds a read-only SDK path to produce a pinned Babysitter
FlowExtensionSubmissionfor the server-owned Software Factory catalog, without publishing an artifact or enabling runtime Babysitter.exportBabysitterCatalogBundlereusesresolveExtensionSubmissionto fetch a canonicalAgentWorkforce/flowscommit ref, then enforces independently supplied bundle/manifest SHA-256 pins, Software Factory compatibility, the native permission shape (GitHub + Codex, no MCP, onlycloud:babysitter-turn), and handlers-only manifests. It returns digest-bound manifest bytes and does not execute handler code. A small CLI writes JSON withwxso failed validation or duplicate runs cannot truncate an existing export.Vitest covers pin drift, mutable refs, overbroad manifests, byte preservation, and CLI EEXIST / no-output-on-failure behavior.
docs/BABYSITTER-CATALOG-HANDOFF.mddocuments export steps, catalog insertion targets, and explicit blockers (native handler, catalog provenance, lineage/receipts); committedevidence/captures build/test runs.Reviewed by Cursor Bugbot for commit b74fb5b. Bugbot is set up for automated code reviews on this repo. Configure here.