Repository navigation
release(skills): publish calle 1.0.4 OAuth setup guidance - #179
Merged
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
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.
Keep MCP connection setup separate from API Key acquisition and storage. Native MCP managers handle OAuth discovery directly; any host-required OAuth fields or allowed hosts come from actual server metadata and the host schema. A separately hosted OAuth authorization server remains part of MCP and is validated separately from the configured MCP server URL.
Prepare standalone
calle1.0.4, synchronizing Skill/evaluation metadata and current installation references. Preserve MCP-first routing, explicit interface choices, fallback conditions, and existing-call recovery. npm and plugin versions are unchanged.Validation:
f0755a90f86a3e9cfa2277a37ce6bc66769c8dce122be8dacd7e8cf325b4a316; the four-file compatibility ZIP matches its published artifact.NOT_RUN. A pre-versioning Muse candidate was installed and its native card showed an added connection, with MCP connection success reported; terminal call results and the full tool inventory were not observed. This is not complete live acceptance of the 1.0.4 artifact.After successful CI, publish the accepted commit under immutable tag
skills/calle@1.0.4with complete ZIPs, a source/artifact manifest, and SHA-256 checksums. Evidence and limits:docs/verification/calle-1.0.4-oauth-setup-2026-11-02.md.