release(skills): publish calle 1.0.3 with MCP-first setup

.changeset/calle-mcp-first-routing.md

@@ -0,0 +1,19 @@
+---
+---
+
+Release independently distributed standalone `calle` `1.0.3` as a patch:
+default new tasks to MCP in supporting hosts, including authorized setup
+and OAuth when the CALL-E connection is missing. Inspect native connection or
+custom-connector management before declaring MCP unsupported. When the Agent
+cannot complete a setup step, provide the remaining user step without switching
+to API Key setup.
+
+Preserve explicit interface choices, existing-call recovery and pre-write API
+fallback for an explicitly unsupported host or a required capability confirmed
+missing by complete discovery. Add synthetic routing cases for missing connectors
+with native or user-managed setup and synchronize current documentation.
+
+No npm package or plugin version bump is needed. Synchronize current Skill and
+evaluation metadata and installation guidance at `1.0.3`, and publish the
+complete source and ZIP under the immutable `skills/calle@1.0.3` tag. Offline
+checks and publication do not establish Muse activation or live acceptance.

AGENTS.md

@@ -35,7 +35,7 @@ Productized OpenClaw skill source lives in `packages/openclaw-cli-skill/skills`.
 
 Before changing standalone Skill identities, install/update origins or migration
 checks, follow [the staged migration plan](docs/calle-skill-migration-plan.md).
-The standalone entries are `calle` version `1.0.2` for the MCP/API workflow and
+The standalone entries are `calle` version `1.0.3` for the MCP/API workflow and
 `calle-cli` for CLI compatibility; CLI and plugin names remain `calle`. Preserve historical verification
 records and add new candidate evidence rather than relabeling earlier runs.
 

README.md

@@ -115,7 +115,7 @@ Choose the integration path that fits your use case:
 ```text
 Install CALL-E for me: https://raw.githubusercontent.com/CALLE-AI/call-e-integrations/main/docs/install/CALL-E-installation-guide.md
 ```
-The linked guide installs the standalone `calle` 1.0.2 Skill and selects the
+The linked guide installs the standalone `calle` 1.0.3 Skill and selects the
 host-supported connection path. The initial live acceptance baseline is Codex
 MCP; API and other clients identify unexecuted live checks separately.
 
@@ -127,7 +127,7 @@ see [calle installation](docs/install/calle.md). Business operations and updates
 use non-CLI host facilities. MCP setup prefers native host management, with a
 limited exception for the current host's official MCP management commands.
 
-The standalone Skill is now `calle` version `1.0.2`. Users retaining the legacy
+The standalone Skill is now `calle` version `1.0.3`. Users retaining the legacy
 CLI workflow can install `calle-cli` through the
 [compatibility guide](docs/install/skills-sh-skill.md#existing-calle-users).
 Plugin-owned `calle` Skills have independent installation and release lifecycles.
@@ -502,7 +502,7 @@ This is a multi-ecosystem integration monorepo with packaged plugins and standal
 | `packages/openclaw-cli-skill` | OpenClaw CALL-E skill source. |
 | `packages/skills-sh-skill` | skills.sh compatible CALL-E skill package. |
 | `skills/calle-cli/` | Portable CLI compatibility Skill; official installation uses `--skill calle-cli`. |
-| `skills/calle/` | Canonical standalone Skill at version 1.0.2; prefers host-managed OAuth MCP, with direct HTTPS/API Key fallback governed by the [interface selection rules](docs/install/calle.md#choose-the-interface). |
+| `skills/calle/` | Canonical standalone Skill at version 1.0.3; prefers host-managed OAuth MCP, with direct HTTPS/API Key fallback governed by the [interface selection rules](docs/install/calle.md#choose-the-interface). |
 | `tests/` | Offline standalone Skill validation and Agent/mock scenario definitions; execution states are recorded separately. |
 | `examples/` | Runnable MCP client demos. |
 | `docs/` | Integration guides, install docs, and troubleshooting. |

docs/agent-integration-layout.md

@@ -9,12 +9,12 @@ This repository is a multi-ecosystem integration monorepo.
 - Keep shared local capability in `packages/cli`.
 - Keep package-scoped, productized skills under their owning package.
 - Keep the skills.sh CLI compatibility `calle-cli` Skill at the repository root in `skills/`.
-- Keep the canonical standalone `calle` source alongside it in `skills/`. It prefers
-  host-managed OAuth MCP and can select direct HTTPS/API Key before business
-  writes when the host explicitly lacks MCP support, the target MCP connection
-  is confirmed not configured, or complete discovery confirms the required
-  capability is missing. Authentication failure or cancellation does not trigger
-  fallback.
+- Keep the canonical standalone `calle` source alongside it in `skills/`. It uses
+  host-managed OAuth MCP in supporting hosts, including authorized setup of a
+  missing connection. It can select direct HTTPS/API Key before business writes
+  when the host explicitly lacks MCP support or complete discovery confirms the
+  required capability is missing. Missing connections, unloaded tools,
+  authentication failure or cancellation do not trigger fallback.
   Business operations and updates use non-CLI host facilities. MCP setup prefers
   the current host's native management capabilities, with a limited official
   host-command exception defined in
@@ -42,7 +42,7 @@ Current standalone layout:
 
 ```text
 skills/calle-cli/  # Official CLI compatibility entry
-skills/calle/      # Canonical MCP/API Skill at version 1.0.2
+skills/calle/      # Canonical MCP/API Skill at version 1.0.3
 ```
 
 Current Claude Code layout:
@@ -161,7 +161,7 @@ intentionally exposes multiple CALL-E marketplaces in the same client UI.
 
 The [migration plan](calle-skill-migration-plan.md) records the formal standalone
 cutover to `calle` `2.0.0`. The current canonical MCP/API Skill is `calle` version
-`1.0.2`, with directory, frontmatter, display name and invocation aligned to
+`1.0.3`, with directory, frontmatter, display name and invocation aligned to
 `calle`. `calle-cli` remains the legacy CLI compatibility entry. The temporary
 installable `callev2` source is retired; its historical verification records
 retain their original inputs.

docs/calle-skill-migration-plan.md

@@ -16,7 +16,7 @@ This is a maintainer-selected version reset, not a numeric upgrade from `2.0.1`.
 Record it in an empty Changeset; no npm package version bump is needed.
 
 The existing numeric updater does not offer older remote versions. Users with
-`2.0.x` installed must explicitly install the current complete `1.0.2` release
+`2.0.x` installed must explicitly install the current complete `1.0.3` release
 and verify host loading before receiving subsequent `1.x` update offers. Follow the
 [installation guidance](install/calle.md#version-designation-and-existing-20x-installations).
 Publication, installation, skills.sh indexing and security audit freshness remain

docs/documentation-maintenance.md

@@ -26,7 +26,7 @@ commands.
   install, migration and local ZIP guidance lives in `docs/install/calle.md`.
   Keep `docs/install/callev2.md`, `docs/install/calle-connect.md` and
   `docs/install/dual-skills.md` as pointers for earlier links. The canonical
-  identity is `calle` with metadata/evaluation version `1.0.2`; the cutover scope
+  identity is `calle` with metadata/evaluation version `1.0.3`; the cutover scope
   is recorded in `docs/calle-skill-migration-plan.md`. The Skill's
   metadata version is independent of the CLI-based skills.sh package attribution.
   Shared routing and business workflow live in `SKILL.md`; MCP and API contracts
@@ -35,6 +35,10 @@ commands.
   repository evaluation policy aligned with it. Keep pre-execution fallback,
   explicit interface choice, incomplete discovery, authentication failures and
   unknown write outcomes synchronized with evaluation scenarios.
+  New tasks default to MCP in supporting hosts, including authorized connection
+  setup and OAuth. Missing connections, unloaded tools and unavailable Agent
+  management capabilities require MCP setup, discovery or a user handoff rather
+  than API Key fallback.
   This customer Skill supports production only, with fixed MCP endpoint
   `https://seleven-mcp-sg.airudder.com/mcp/openagent_oauth` and API base URL
   `https://api.heycall-e.com`. Keep setup, templates, manual checks, and repository
@@ -116,7 +120,7 @@ commands.
   attribution `skills_sh/skills_sh_skill/<version>`, authentication and recovery
   paths. Plugin names and package-scoped `calle` Skills are separate surfaces.
 - The stable `docs/install/CALL-E-installation-guide.md` defaults to `calle`
-  `1.0.2` and must remain at that path. Codex MCP is the initial live acceptance
+  `1.0.3` and must remain at that path. Codex MCP is the initial live acceptance
   baseline; API and other clients must identify unexecuted live checks.
 - Repository-local Codex helper skills live in `.agents/skills/`.
 

docs/install/calle-connect.md

@@ -1,7 +1,7 @@
 # Earlier calle-connect Installation Guide
 
 The current canonical standalone MCP/API workflow is
-[`calle` 1.0.2](calle.md). Follow that guide for complete installation, host
+[`calle` 1.0.3](calle.md). Follow that guide for complete installation, host
 requirements, interface selection, updates and validation scope. The legacy
 CLI workflow remains available through [`calle-cli`](skills-sh-skill.md).
 

docs/install/calle.md

@@ -1,11 +1,12 @@
 # Install the calle Skill
 
 [`calle`](../../skills/calle/SKILL.md) is one standalone Skill for
-CALL-E calling workflows. It prefers host-managed OAuth MCP. Before business
-writes, it can select direct HTTPS with an API Key when the host explicitly lacks
-MCP support, the target MCP connection is confirmed not configured, or complete
-discovery confirms the required capability is missing. Authentication failure or
-cancellation does not trigger fallback. The source metadata version is `1.0.2`.
+CALL-E calling workflows. When the host supports MCP, new tasks default to
+host-managed OAuth MCP, including authorized setup of a missing connection.
+Before business writes, it can select direct HTTPS with an API Key when the
+host explicitly lacks MCP support or complete discovery confirms the required
+capability is missing. Missing connections, unloaded tools, authentication
+failure, or cancellation do not trigger fallback. The source metadata version is `1.0.3`.
 The directory, Skill name and display name are `calle`; invoke it as `$calle`.
 This is the canonical standalone Skill. The CLI executable and plugin-owned
 `calle` Skills have independent installation and release lifecycles.
@@ -47,7 +48,7 @@ with their original contents.
 Version checks compare numeric versions and do not offer downgrades. Existing
 `2.0.x` installations therefore do not receive automatic offers for `1.0.0` or
 later `1.x` versions. To move to this release sequence, explicitly install the
-complete `1.0.2` Skill using the source or ZIP procedure below, then reload the
+complete `1.0.3` Skill using the source or ZIP procedure below, then reload the
 host and verify the loaded version. Preserve local edits, account configuration
 and saved call records under the existing installation and rollback guidance.
 
@@ -107,7 +108,8 @@ their host's supported interface. Do not invent a hosted ZIP URL.
 | --- | --- |
 | The user explicitly chooses MCP or API | Honor that choice; do not silently switch. |
 | Connected MCP tools support the operation | Prefer MCP. |
-| The host explicitly lacks MCP support or the target connection is confirmed not configured | Use API before business writes if the API supports the operation and safe credentials and HTTP capability are available; otherwise complete authorized setup or explain what is missing. Authentication failure or cancellation does not meet this condition. |
+| The host supports MCP but the target connection is missing | Select MCP and complete authorized connection setup, OAuth and tool loading. Inspect native connection or custom-connector management even if no CALL-E connector is installed. If the Agent cannot complete a step, give the confirmed user step; keep MCP selected without requesting an API Key. Check-only, offline and preview requests retain their setup restrictions. |
+| The host explicitly lacks MCP support | Use API before business writes if the API supports the operation and safe credentials and HTTP capability are available; otherwise complete authorized API setup or explain what is missing. An unavailable Agent connection manager does not establish that the host lacks MCP support. |
 | Complete tool discovery confirms MCP does not support the operation | Select API before business writes, after checking its operation support, production endpoint, and account. |
 | Discovery is incomplete or tools are not yet loaded | Refresh or complete discovery; do not treat this as unsupported capability. |
 | OAuth expires, access is denied, or authorization is cancelled | Handle the authentication or permission result; do not automatically switch credentials. |

docs/install/callev2.md

@@ -1,7 +1,7 @@
 # Retired callev2 Testing Guide
 
 The temporary `callev2` testing identity has been retired. Install the canonical
-[`calle` 1.0.2 Skill](calle.md) for the current standalone MCP/API workflow, or use
+[`calle` 1.0.3 Skill](calle.md) for the current standalone MCP/API workflow, or use
 [`calle-cli`](skills-sh-skill.md) to retain the legacy CLI workflow.
 
 Migration of installed `callev2` copies is outside this release's scope. This

docs/install/dual-skills.md

@@ -1,7 +1,7 @@
 # Earlier Dual-Skill Installation Guide
 
 The earlier separate API and MCP entries were merged during testing. The current
-canonical standalone workflow is [`calle` 1.0.2](calle.md), which prefers MCP
+canonical standalone workflow is [`calle` 1.0.3](calle.md), which prefers MCP
 and supports API Key access under its interface selection rules. Users retaining
 the legacy CLI workflow can install [`calle-cli`](skills-sh-skill.md).
 

docs/install/install-guide.md

@@ -23,7 +23,7 @@ its own environment.
 
 <!-- sync-with: docs/install/calle.md#install-the-source-or-zip -->
 
-Install the canonical standalone `calle` `1.0.2` Skill globally from the
+Install the canonical standalone `calle` `1.0.3` Skill globally from the
 repository root:
 
 ```bash

docs/install/skills-sh-skill.md

@@ -4,7 +4,7 @@ This guide covers the CLI-based `calle-cli` skill. Its source of truth lives at
 `skills/calle-cli` so skills.sh can index the public skill page and search results
 directly from the repository root.
 
-For the default standalone `calle` 1.0.2 Skill, which prefers MCP with API Key fallback,
+For the default standalone `calle` 1.0.3 Skill, which prefers MCP with API Key fallback,
 see [calle installation](./calle.md) and its
 [interface selection rules](./calle.md#choose-the-interface).
 Business operations and updates use non-CLI host facilities. MCP setup follows

docs/install/troubleshooting.md

@@ -2,7 +2,7 @@
 
 ## Which standalone Skill is installed?
 
-The canonical standalone MCP/API Skill is [`calle` 1.0.2](calle.md). Verify its
+The canonical standalone MCP/API Skill is [`calle` 1.0.3](calle.md). Verify its
 loaded name and version after host reload, not just its directory on disk.
 Plugin-owned `calle` entries have separate lifecycles; identify the intended
 standalone or plugin entry when the host exposes overlapping names.

docs/skill-update-mechanism.md

@@ -1,17 +1,18 @@
 # Standalone Skill Update Mechanism Design Record
 
 Design first recorded on 2026-10-15. Current guidance applies to the canonical
-standalone `calle` entry, metadata/evaluation version `1.0.2`; the dated
+standalone `calle` entry, metadata/evaluation version `1.0.3`; the dated
 third-party audit examples below remain historical snapshots. The selected
 repository is `CALLE-AI/call-e-integrations`.
 
 The mechanism lets an Agent read the version from the official remote
 `SKILL.md` when using an installed Skill, compare it with the local version, and
 ask whether the user wants to download a newer version. Business operations
-prefer MCP; API Key fallback is selected only before business writes, when the
-host explicitly lacks MCP support, the target MCP connection is confirmed not
-configured, or complete discovery confirms the required capability is missing.
-Authentication failure or cancellation does not trigger fallback. Update checks
+use MCP in supporting hosts, including authorized setup of missing connections;
+API Key fallback is selected only before business writes, when the host
+explicitly lacks MCP support or complete discovery confirms the required
+capability is missing. Missing connections, unloaded tools, authentication
+failure or cancellation do not trigger fallback. Update checks
 do not depend on business interfaces or introduce a CLI, SDK, new MCP tool, or version
 lookup service.
 
@@ -193,7 +194,7 @@ requires review.
 
 The earlier MCP/API merge was tested as `calle-connect` version `0.2.0`.
 The formal cutover promoted the `callev2` `2.1.1` implementation to `calle`
-`2.0.0`. The current canonical `calle` version is `1.0.2`, with evaluation inputs
+`2.0.0`. The current canonical `calle` version is `1.0.3`, with evaluation inputs
 at `tests/behavior/calle-evals.json`.
 Keep historical acceptance tied to its original names and hashes; source binding
 and host activation need candidate-specific evidence under the

docs/verification/calle-1.0.3-mcp-first-2026-11-02.md

@@ -0,0 +1,59 @@
+# calle 1.0.3 MCP-first verification
+
+Date: 2026-11-02 (Asia/Shanghai).
+
+## Candidate scope
+
+The independently distributed standalone `calle` Skill changes its default route
+to MCP whenever the host supports it, including authorized setup and OAuth for a
+missing connection. An absent CALL-E connector, unloaded tools or unavailable
+Agent management access requires setup, discovery or a user handoff. These
+conditions no longer permit automatic API Key fallback.
+
+Explicit interface choices, existing-call recovery, authentication and permission
+boundaries, and fallback before business writes for an explicitly unsupported
+host or a capability confirmed missing by complete discovery remain in place.
+Current metadata, evaluation versions and installation guidance use `1.0.3`.
+CLI, plugin and npm package versions are unchanged.
+
+## Local validation
+
+| Check | Result |
+| --- | --- |
+| Repository version, syntax and metadata checks | PASS |
+| Full Node/package suite through Corepack pnpm 10.18.3 | PASS |
+| `.venv/bin/python -m tests.run_offline` | PASS: 274 tests |
+| `pnpm pack:skill:calle` | PASS: complete 19-file Skill |
+| `pnpm pack:skill:calle-cli` | PASS: unchanged four-file compatibility Skill |
+| `pnpm pack:dry-run` | PASS |
+| ZIP CRC, file inventory and byte comparison with source | PASS for both ZIPs |
+| Added and rewritten repository text | English; historical verification records preserved |
+
+The initial full Node run encountered a local mise `npm` shell wrapper that the
+mixed-install test tried to execute as JavaScript. The affected test and full
+suite passed with a temporary PATH entry pointing directly to the installed npm
+JavaScript entry point. No repository or global tooling change was needed.
+
+| Artifact | SHA-256 |
+| --- | --- |
+| `calle.zip` | `038f26547d42f06482b6775799608b3d278a9179d1629e3a2b5dfdf13db77e65` |
+| `calle-cli.zip` | `40a2fdde2640b13997bdf4e29804498060494c239fd87526d9e647f6871bc23b` |
+
+The compatibility ZIP hash matches the published `skills/calle@1.0.1` artifact.
+The release manifest binds the final publication revision, source file hashes
+and ZIP hashes to the immutable `skills/calle@1.0.3` tag. GitHub CI and public
+delivery are verified separately from these local checks.
+
+## Unexecuted acceptance
+
+The new `route-15` native-custom-connector, user-managed-setup and
+unknown-host-support variants are synthetic definitions marked `NOT_RUN` until
+an Agent is evaluated. Offline fixture checks do not establish Muse behavior.
+No fresh Muse installation or activation, OAuth flow, live call, release-specific
+security scan or skills.sh index refresh is established by this record.
+
+## Release decision
+
+Patch release recommended for standalone `calle`, prepared as `1.0.3`.
+The empty-package Changeset `calle-mcp-first-routing.md` records this independent
+release; no npm package or plugin version bump is included.