"Debundle" Sparkle, fix agent extension release #102
Merged
Conversation
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
- Add Extension Discovery and Recommendations section to extensions.md - Extension source naming (crate, acp, url) - Crate-defined recommendations - External recommendations format - Discovery flow documentation - Create Crate Author's Guide section with three chapters: - Creating Extensions: MCP server basics, Cargo.toml metadata - Publishing Extensions: ACP registry submission - Recommending Extensions: central and crate-based recommendations - Add WIP tracking for extension discovery implementation - Reorganize SUMMARY.md: - New 'Crate Author's Guide' section for extension authors - Rename 'Development guide' to 'Contributing to Symposium' - Add 'Work in Progress' section Co-authored-by: Claude <claude@anthropic.com>
- Rename 'extensions' to 'agent extensions' throughout - Explain that agent extensions are ACP proxies, not MCP servers - Lead with crates.io as primary distribution, ACP registry as optional - Use Sparkle as example of general-purpose extension - Link to sacp-cookbook for implementation details Co-authored-by: Claude <claude@anthropic.com>
Sparkle is now installed on first use via cargo-binstall from crates.io,
rather than being compiled into symposium-acp-agent. This:
- Reduces binary size
- Enables automatic updates when new sparkle-mcp versions are published
- Demonstrates the cargo distribution path for extensions
Binaries are cached at ~/.symposium/bin/sparkle/{version}/bin/sparkle-mcp.
On each run, we query crates.io for the latest version and install if needed.
Co-authored-by: Claude <claude@anthropic.com>
- Add ci/sync-versions.sh script to update package.json and extension.toml - Update release-plz workflow to run sync after creating release PR - Sync versions to 1.3.0 (matching current symposium-acp-agent release) The sync script updates: - vscode-extension/package.json version field - zed-extension/prod/extension.toml version field - zed-extension/prod/extension.toml archive URLs Co-authored-by: Claude <claude@anthropic.com>
Tests the actual sparkle-mcp installation via cargo binstall using a temp directory. Verifies the binary exists and is executable. Co-authored-by: Claude <claude@anthropic.com>
- Exclude sparkle from test workspace extensions to avoid cargo-binstall timeout in CI (sparkle is now installed on-demand, not compiled in) - Pin VS Code test version to 1.108.0 for reproducible tests - Cache VS Code test download in CI to speed up test runs Co-authored-by: Claude <claude@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This change moves Sparkle so that it is "cargo binstall"'d, taking advantage of our new ability to have "cargo" agent extensions, and improves CI somewhat to fix the Zed extension + automate release of new extensions.