[djbriane]

Summary

• Mirror mailgun-mcp-server publish.yml: a published GitHub Release whose tag is v plus package.json version runs test, then npm publish --access public --provenance via OIDC trusted publishing.
• Mirror mailgun-mcp-server ci.yml test matrix (Node 20/22/24). Lint is omitted because this repo has no lint script yet.
• Same package hooks and metadata as MCP: prepublishOnly build, .nvmrc 24.15.0, repository / homepage / bugs. Build is not a separate workflow step; npm publish runs prepublishOnly, matching MCP.
• Fix the test script so it runs on Node 20. node --test only accepts glob patterns as of Node 21.0.0, so "dist-test/**/*.test.js" was read as a literal path (Could not find .../dist-test/**/*.test.js). The compiled test files are now passed explicitly. This bug predates this PR; the new CI matrix is simply the first thing to exercise Node 20, which engines and the README both claim support for.
• README now assumes @mailgun/cli is on npm (npm install -g, npx, version badge), matching the MCP server install story. Source build stays under Development.

npm team (one-time)

This PR does not publish. After merge, add an npm Trusted Publisher on @mailgun/cli:

• Organization: mailgun
• Repository: mailgun-cli
• Workflow filename: publish.yml
• Environment: empty

Then bump version on main and create GitHub Release vX.Y.Z.

Test plan

• CI test job green on Node 20, 22, and 24 (143 tests)
• Workflow has no NPM_TOKEN / NODE_AUTH_TOKEN
• README install path is npm/npx, not source-only
• Trusted Publisher configured for @mailgun/cli → mailgun/mailgun-cli / publish.yml
• First publish uses a tag that matches package.json (v0.2.0 or next)