Repository navigation
feat: add Batuta to marketplace - #432
Conversation
|
@franciscpd is attempting to deploy a commit to the Compozy Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. WalkthroughAdded an MIT License file for the Batuta package. The file includes a 2026 copyright notice, permission terms, attribution requirements, and warranty and liability disclaimers. ChangesBatuta licensing
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🔵 Low · up to The PR adds a vendored Batuta marketplace extension, but copyright ownership and notice requirements for the included release still need confirmation before merge. This is a bounded legal/compliance risk that is mergeable with explicit owner follow-up. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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 |
|
| Filename | Overview |
|---|---|
| catalog/extensions.json | Registers the Batuta community release and its pinned artifact metadata; no catalog-entry defect was established. |
| catalog/packages/batuta/agents/batuta/AGENT.md | Defines the Batuta conductor workflow, including the intended originating-session handoff and delivery controls. |
| catalog/packages/batuta/loops/batuta-deliver/loop.yaml | Adds the implementation-and-review loop, but its terminal callback trusts a caller-selected session destination. |
| catalog/packages/batuta/resources/skills/batuta-routing/SKILL.md | Documents catalog-derived cost and complexity routing with stored workspace overrides. |
| catalog/packages/batuta/extension.toml | Declares the extension version, compatibility floor, and resource directories without an established defect. |
Reviews (1): Last reviewed commit: "feat: add Batuta to marketplace" | Re-trigger Greptile
| - &return_to_origin | ||
| tool: compozy__session_prompt | ||
| with: | ||
| session_id: "{{ .inputs.origin_session_id }}" |
There was a problem hiding this comment.
Unbound terminal prompt destination
When a direct submission supplies another same-workspace session as origin_session_id, every terminal handler sends that session a daemon-authorized prompt instructing it to inspect and report child-run IDs, commits, and blockers. The prompt handler and loop_status enforce only workspace scope, so this permits cross-session instruction injection and run-metadata disclosure. How this was verified: The supplied destination survives daemon dispatch binding, the prompt handler checks only workspace membership, and loop-status lookup permits any session in that workspace to read the referenced run.
What & why
The vendored Markdown and YAML are normalized with the repository formatter; the manifest and functional resource content remain aligned with the published Batuta release.
How you verified it
go run ./cmd/compozy-catalog validate ./catalog— production installer validation passed.go test ./cmd/compozy-catalog ./internal/marketplace— 160 tests passed.make gatewith Go 1.26.4 and an ephemeraltag.gpgsign=falsetest override — full gate passed, including 23,288 Go tests with 3 platform skips.No new test file is needed: the existing catalog validator installs every pinned local artifact, verifies its digest, loads the extension manifest, and checks the feed version.
Impact
Marketplace extension catalog only. No CLI, HTTP/UDS, configuration, or web contract changes. After merge and catalog refresh, Batuta installs from the curated
communitytier and still requires explicit enablement before publishing its resources.Prepared with Codex and verified against the complete repository gate.
make gatepasses locally (make gate-fullbefore review on larger changes)Summary by CodeRabbit