Claude Code install proof — aeat plugin¶
Live verification record for the claude-ecosystem-packaging campaign (plan step W05.P12.S43). Client: Claude Code CLI 2.1.199 on Windows 11, 2026-07-03. Every command below ran for real; outputs are quoted from the live run.
What was proven¶
Generate.
aeat app agent --layout plugin -o <dir>materialised the plugin from the shipped harness source: 34 skills, 7 agents, aeat v0.1.0.Validate.
claude plugin validate --strictpassed on the plugin tree AND on the composed marketplace tree (thepackaging/marketplacemanifest + the generated plugin underplugins/aeat).Marketplace add.
claude plugin marketplace add <marketplace-dir>→ “Successfully added marketplace: aeat-marketplace”.Install.
claude plugin install aeat@aeat-marketplace→ “Successfully installed plugin: aeat@aeat-marketplace (scope: user)”. Two designed behaviours surfaced exactly as decided:defaultEnabled: false— the client reported the plugin installs disabled and named the enable command;the persona
userConfigoption was detected — “1 userConfig option not yet set”, configurable via/plugin configureor--config KEY=VALUE.
Server starts (dev-env proof). The stdio
aeat-mcpserver passes the real-client handshake conformance tests (initialize / tools-list / call round-trip): 2 passed.
What remains blocked, and on what¶
The installed plugin’s .mcp.json launches the server as
uvx --from aeat==0.1.0 aeat-mcp. Until the first aeat wheel is published
to PyPI (RELEASING.md, name-claim sequencing — an operator-gated step
needing a PyPI account and scoped token), uvx cannot resolve that
requirement on any machine, so the end-to-end
installed-plugin-starts-the-server link is unverifiable by design. The
moment the wheel is on PyPI, re-run: enable the plugin, start Claude Code,
and confirm the aeat MCP server’s tools list loads; then update this
record.
Verified support matrix contribution¶
Client |
Marketplace install |
Plugin config UX |
Local stdio server |
|---|---|---|---|
Claude Code CLI |
PASS (live) |
PASS (live) |
Handshake PASS from dev env; uvx path pending first publish |