chore(plugins): publish support@agents.e2a.dev as the contact address

[jiashuoz]

What

The published contact address on the plugin author block and the marketplace owner block moves from support@e2a.dev to support@agents.e2a.dev.

Edited in plugins/e2a/plugin.meta.json and plugins/e2a-labs/plugin.meta.json — the single source of truth — then regenerated. .claude-plugin/marketplace.json is the only downstream manifest that emits the address.

Two consequential changes ride along, both required by gates rather than chosen:

• Version bumps. check-plugin-version-bump.mjs requires every changed plugin to bump. Metadata-only, so patch: e2a 0.9.4 → 0.9.5, e2a-labs 0.3.0 → 0.3.1. Regenerating propagates them through the per-client manifests.
• Test pins. plugin-packaging.test.mjs and plugin-email-evals.test.mjs assert the released version as a literal across every generated manifest, so a bump is only half-applied until they move with it.

Why

support@e2a.dev was the one public support address matching nothing else we publish. Everywhere else the hosted deployment already uses support@agents.e2a.dev — notifications.reply_to in config.prod.yaml, FEEDBACK_NOTIFY_TO in the feedback fan-out, and NEXT_PUBLIC_FEEDBACK_EMAIL on the dashboard. That address is a real e2a agent on a domain with a live MX, which is also what the fan-out's "target must be an existing agent" constraint requires.

support@e2a.dev depended instead on a Cloudflare Email Routing forward on the apex, with nothing in either repo pinning that rule — so a directory listing was sending people to an address whose delivery path wasn't owned anywhere. It also dogfoods the product: the support inbox for an agent-email company is an agent inbox.

This does not revisit the 2026-08-08 decision (e2a-ops#295) that kept support@agents.e2a.dev over support@team.tokencanopy.com — it brings the last stray reference into line with it.

Worth knowing

The labs version pin at plugin-packaging.test.mjs:67 was masked by assertion order: assert.equal on the core version throws first, so the 0.3.0 pin two blocks below never ran. The first CI failure reported only the core mismatch; the labs one would have surfaced on the next push. Both are fixed here.

Not touched

• scripts/validate-plugin.test.mjs — support@e2a.dev there is a minimal valid-shaped fixture in synthetic base metadata, not a published address. Those tests assert schema and freshness, never the value.
• plugins/e2a-labs/skills/agentify/examples/e2a/autonomous-repo.config.yml — an example config whose support_address carries an explicit TODO(open-q #6): confirm verified domain, alongside a second open TODO on approver. Resolving one and leaving the other reads worse than leaving the pair for the open question that owns them.
• design-system/src/Avatar/Avatar.stories.tsx — a Storybook avatar fixture demonstrating initials-from-email, not a contact.

Verification

• node scripts/generate-plugin-manifests.mjs → 9/12 manifests updated; every generated file regenerated, never hand-edited.
• node scripts/validate-plugin.mjs → green, freshness gate included (a hand-edited generated manifest is exactly what it fails on).
• node --test over the workflow's exact six-file list → 67/67 pass.
• grep -rn 'support@e2a.dev' --include='*.json' on the branch → no matches.
• Full PR CI: 24/24 green.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JS3LokLt1bMyMwi8Aa1Td7