ea-plugin-cli

Encre Agent Plugin Market Unified CLI

PyPI | Changelog

The single toolchain that takes a plugin from scaffold to the central registry. After publishing, the registry CI merges catalog entries into the ea-cwh index package, which the market backend renders locally.

🤖 What is ea-plugin-cli?

encre-plugin covers the full plugin lifecycle for the Encre Agent plugin market:

• Scaffold — generate a ready-to-publish ea-plugin-<name> package skeleton
• Build — enforce central-registry policy, compile a wheel, digest every artifact
• Verify — smoke-test the wheel in an isolated venv (install, import, manifest probe)
• Publish — upload to PyPI, then open the central-registry catalog PR automatically

Installation

Ready to run: python build.py cli compiles a single-file executable for the
current platform (build/cli/encre-plugin[.exe] — no pip install required; it
shells out to a host Python found on PATH for build/venv/twine and
auto-installs any missing components on first use)

Or as a module: pip install ea-plugin-cli   # development: pip install -e cli/

⭐ Commands

📦 publish ↔ Central Registry

• --registry-dir <dir> — use an existing registry checkout; when omitted, the CLI clones https://github.com/mf2023/ea-cwh.git into a local cache (%LOCALAPPDATA% / ~/.cache → encre-plugin-cli/registry) and hard-syncs it to origin/main every run
• --registry-url <git url> — override the default remote (point at a fork or a local bare repository to rehearse the whole flow)
• --no-upload — skip the twine upload, run the registry-PR half only
• --dry-run — print the files that would be uploaded and the catalog entry; no remote action
• The PR branch carries exactly one file (catalog.d/<name>.json): the branch is cut from origin/main before the entry is written, so no dirty worktree state can leak into the PR
• Transition note: verify needs encre-harness to be importable inside the probe venv; for local development either pip install -e harness/ or use --no-deps plus a PYTHONPATH pointing at the source trees

🛡️ Central Registry Policy (enforced at build time)

🔧 Environment Variables

• PyPI credentials: TWINE_USERNAME / TWINE_PASSWORD (CI uses trusted publishing and needs neither)
• The automatic PR requires the registry checkout to have git remote add origin and a logged-in gh CLI

🌏 Community & License

• Issues and PRs are welcome!
• Main repository: https://github.com/mf2023/encre-agent
• Central registry: https://github.com/mf2023/ea-cwh
• CLI repository: https://github.com/mf2023/ea-plugin-cli