Add plugin entry: copilot

[balazstasi]

What the plugin does

Adds Copilot (entries/copilot.json): runs GitHub Copilot CLI as a bb agent provider. The Copilot CLI natively speaks ACP, so the plugin ships no bridge — it provisions a managed customAcpAgents entry registering provider acp-copilot.

Source release

• Repository: https://github.com/balazstasi/bb-plugin-copilot
• Release: tag v0.1.0 (commit 7594326), entry range ^0.1.0, no subdirectory, no tag prefix
• Plugin id derived from package name bb-plugin-copilot → copilot; matches the entry id

Plugin checks that succeeded

• npm install clean (0 vulnerabilities), tsc --noEmit, vitest run 5/5
• bb plugin build against the packaged bb CLI produces dist/server.js + dist/app.js
• End-to-end against a live bb dev instance: install → provision service running → provider listed → models negotiated over ACP → live turn completed

Marketplace checks that succeeded

• npm ci --ignore-scripts, npm run build and npm run check (liveness) — built manifest includes the new entry (64 entries)
• Entry validated against schema/marketplace.schema.json: exact required fields only, tags match the pattern, icon vendored at icons/copilot-7133b161.svg (sha256 prefix 7133b161, ~1.7 KB SVG)

Security / permission notes for reviewers

• The plugin is full-trust bb server code. Its only write surface is a single managed customAcpAgents entry in the user's bb config.json; it merges managed fields over existing keys, preserves unknown user keys, and writes atomically.
• It executes copilot --version to probe PATH; it never reads or writes Copilot credentials.
• No network calls beyond spawning the local CLI; no telemetry.

AGENT GENERATED: by ox-alpha

[SawyerHood]

Automated note from a Claude Code agent, posted on behalf of the marketplace maintainer.

Thank you for building a Copilot provider. We are rejecting this version for now while BB changes its provider API.

The current provider API remains experimental. We are making it a more first-class API, so please wait until that work stabilizes.

• The current implementation replaces the full BB configuration file (server.ts:50-74).
• The atomic replacement does not keep the existing 0600 mode (src/config-entry.ts:78-82). It can create a group-readable file.

After the provider API stabilizes, please use the supported API. If a file change remains necessary, keep the existing mode and protect concurrent changes.

[SawyerHood]

Automated note from a Claude Code agent, posted on behalf of the marketplace maintainer.

We are requesting changes for the reasons in the automated review comment above. Please reply after a new matching release is available.

[balazstasi]

"The current provider API remains experimental. We are making it a more first-class API, so please wait until that work stabilizes."

Where can I follow this? @SawyerHood