[OlegNickeshin]

Plugin type (required)

• UI Plugin
• Standard plugin
• Not applicable

Affected manifest name: lemma-telepath. The hosted MCP exposes an interactive photo-viewing resource through _meta.ui.resourceUri; this submission adds no local UI code.

What this adds

Lemma Telepath connects the user's Telegram archive to ZCode through a hosted MCP server. Users can search conversations, read messages, documents, photos and voice transcripts, and send replies with their permission. Authentication uses Telegram through OAuth; the MCP endpoint is https://telepath.lemma.company/mcp.

Registration and intake fix

The package is now under external_plugins/lemma-telepath/, and its marketplace source is ./external_plugins/lemma-telepath, as required by the external-submission validator. The branch is rebased onto upstream main e419489; the shared catalog conflict is resolved with every existing upstream entry preserved.

The four package files (.zcode-plugin/plugin.json, .mcp.json, README.md, README_CN.md) are byte-for-byte identical to the previous submission. Version remains 0.1.0 in the manifest and catalog because the installable content has not changed. Only the package's repository location and its catalog source path changed. No other plugins, scripts, workflows or repository rules are modified.

Validation — 2026-10-25

• pnpm install --frozen-lockfile — passed with Node 24.22.1 and pnpm 10.33.2.
• python3 scripts/validate.py — passed: 52 plugins.
• git diff --check — passed.
• Built Telepath's ZIP using the repository's build_dist.build_zip; verified all four archived files against the previous submission, byte-for-byte.
• pnpm build — blocked by the unrelated upstream PhotoCraft build, which requires rustup, unavailable in this environment.
• python3 scripts/build_dist.py — consequently stops on PhotoCraft's incomplete build. Telepath's own package builds successfully; shared build scripts were not modified.

The original submission was exercised in ZCode 3.14.4 on Linux: plugin installation, OAuth registration/sign-in, and reading the user's chat list. That runtime test has not been rerun for this directory-only correction.

Dependencies, permissions and provenance

The package contains manifests and documentation only: no hooks, local executables, commands, agents, skills or install scripts. It connects to the hosted service on telepath.lemma.company for MCP and OAuth. The hosted service uses Telegram's official Business Bot API; it does not use an MTProto user session.

Sending tools have real external effects and send as the user when Telegram Business permissions and its messaging window permit. Access and optional features are controlled through the Telepath bot. The service is not end-to-end encrypted; the package READMEs disclose its server-side processing and storage model.

Package license: MIT, published by Lemma Company at https://github.com/Lemma-Company/telepath-plugin. The hosted service is operated by Lemma under its published terms and privacy policy. No third-party code or assets are vendored in this submission.

[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.

[panda920]

❌ Internal validation failed:

lemma-telepath: external submissions must use ./external_plugins/lemma-telepath

Please fix it and push again; the check re-runs automatically.

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

You are updating my pull request #65 to github.com/zai-org/zcode-plugins (the ZCode plugin marketplace).
The maintainers' automated intake reported: `python scripts/validate.py` failed

Validator output:
lemma-telepath: external submissions must use ./external_plugins/lemma-telepath

Fix it in this repository:
- New external plugins belong under external_plugins/<my-plugin>/; keep existing plugins in their current directory;
  never modify .github/, scripts/, tests/, .gitignore, .gitattributes or AGENTS.md.
- Follow CONTRIBUTING.md and AGENTS.md: the manifest lives at <plugin-directory>/.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; after acceptance, release checks run separately and this PR is closed automatically.