[Upkuajing]

Plugin type (required) / 插件类型（必填）

• UI Plugin / 是 UI 插件
• Standard plugin / 普通插件（非 UI）
• Not applicable / 不适用

Affected plugin name(s) / 涉及的插件名称：upkuajing

What / 改动内容

Add UpKuaJing (跨境魔方) 1.0.6 as a community plugin under external_plugins/upkuajing/, registered in the productivity category. It connects to the hosted HTTP MCP service at https://mcp.upkuajing.com/mcp and includes a skill for B2B company and contact discovery, trade research, lead enrichment, and explicitly requested outreach.

The package includes equivalent English and Chinese READMEs, localized marketplace descriptions and display names, an icon, and an MIT license for the configuration, documentation, and skill. It bundles no local executable scripts, hooks, or server source. An UpKuaJing account and OAuth authorization are required. Paid actions require live pricing and explicit cost confirmation; message delivery also requires approval of recipients and content.

Verification and runtime status

• python3 scripts/validate.py passes for all 51 marketplace entries.
• The focused upkuajing package build passes: its zip contains the MCP declaration, manifest, and skill; the published entry resolves to publisherType=community and componentTypes=[skill, mcp].
• git diff --check upstream/main...HEAD passes.
• The repository-wide pnpm build requires a Rust toolchain for other UI plugins, which is unavailable in this local environment. The full scripts/build_dist.py build is therefore not confirmed locally for this revision.
• Installation, enablement, Chinese display name, and icon display were confirmed in ZCode for the prior package. On September 14, 2026, a maintainer confirmed production OAuth login and account balance retrieval. Installation of the 1.0.6 package, token refresh, and business-result rendering remain unverified; no paid queries or message delivery were performed.

Self-check / 自查清单

• Unique kebab-case name; community source is external_plugins/upkuajing/.
• Plugin type and affected manifest name are declared above.
• plugin.json and marketplace.json both declare version 1.0.6.
• English and Chinese READMEs are equivalent.
• description_i18n includes en and zh-CN.
• No secrets, machine-specific paths, or private dependencies are included.
• Model, API, network dependencies, and side effects are documented.

[panda920]

Thanks for the contribution! This PR no longer applies cleanly on top of the latest main (conflicts in: marketplace.json). Please rebase onto main and push again; it will be picked up automatically.

🤖 Copy this prompt into Claude Code / Codex to fix it

You are updating my pull request #12 to github.com/zai-org/zcode-plugins (the ZCode plugin marketplace).
The maintainers' automated intake reported: the PR conflicts with the latest main

Conflicting files: marketplace.json

Fix it in this repository:
- Only change files under plugins/<my-plugin>/ and my plugin's entry in marketplace.json;
  never modify .github/, scripts/, tests/, .gitignore, .gitattributes or AGENTS.md.
- Follow CONTRIBUTING.md and AGENTS.md: the manifest lives at plugins/<name>/.zcode-plugin/plugin.json,
  its name/version must match marketplace.json, names are kebab-case, keep the required i18n fields.
- Fetch the latest main of zai-org/zcode-plugins and rebase onto it; if marketplace.json conflicts,
  keep every existing entry and re-add mine.
- Run `python scripts/validate.py` until it passes, then force-push my PR branch.

[panda920]

✅ Internal validation passed. A ZCode maintainer will review the change next; once merged it is published to the marketplace and this PR is closed automatically.

[Upkuajing]

Hi maintainers, UpKuaJing 1.0.6 is now under external_plugins/upkuajing/ and rebased onto the current main. The PR is mergeable; the marketplace validator and focused plugin package build pass. The PR description includes the verification details and remaining runtime checks. Could you please review it when convenient? Thank you.

[panda920]

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.