feat: publish plugin-library as an Agent Bundle - #7
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
This was referenced Sep 16, 2026
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.
Summary
cursorandportableprojections withmarketplace: true; remove handwritten Cursor/Claude/Codex/portable manifests and the handwritten installer.agent-bundle-artifactbranch after eachmainupdate, so Cursor can import the repository and track the generated branch without committing build output tomain.src/, compile the sidecar and launcher as artifact scripts, and add package-bound install/doctor plus a clean-consumer smoke.Shape and assumption
plugin-libraryis one sidecar explorer with one skill and one command. Its catalog data describes other plugins, but those rows are data, not separately installable projects in this repository.The requested Grok Bot path is interpreted as the Agent Plugins 1.0.0
portableprojection. The currentgbotCLI has roster/messaging commands but no plugin-install verb, so the gate proves the portableplugin.json+ skill pack and does not claim remote Grok Bot activation. The Cursor slash command is documented as Cursor-only.Cursor's documented GitHub route is a Teams/Enterprise Team Marketplace import: import
https://github.com/ScriptedAlchemy/plugin-libraryand selectagent-bundle-artifact. Existing imports that trackedmainmust re-import the generated branch. The publish workflow creates that branch only after this PR lands, so this PR proves the same generated artifact locally; post-merge verification will fetch the branch from GitHub.Framework version
npm view agent-bundle versionreturned0.1.2, not0.2.1. The lockfile therefore uses the pkg.pr.new revision pinned by cargo-hauler (62ffe403c5af73499fe7f5767c6d60be26e250db).Verification
npm run checkpassed on Node 24.15.0:agent-bundle validateagent-bundle buildagent-bundle validate --artifact artifacttsc -p tsconfig.json --noEmitThe packed smoke installs the generated npm root into a clean prefix/HOME, runs
plugin-library-install install cursor, runs framework Doctor, starts the installed sidecar, fetches/api/library, and stops it. Doctor reported:The informational finding is Cursor's lack of a non-interactive surface for observing enabled/active state.
Independent Fable review found no remaining material merge risk after follow-up fixes. No changeset is included because this package is private. No Agent Bundle framework issue was required.