PR #255 merged: feat: custom_network_aliases (#254) + MCPB one-click bundle + MCP registry auto-publish

Summary

Housekeeping sweep — closes #254 and fixes the stale-distribution problem.

custom_network_aliases on application update (closes #254)

• Added to UpdateApplicationRequest + the application tool zod schema (update only — Coolify's create endpoints don't accept it, matching the dockerfile_target_build precedent).
• Field description documents the gotcha that cost two failed E2E runs: app containers get no stable uuid DNS hostname (only databases do).
• Tests: client PATCH pass-through + MCP tool forwarding.

server.json drift fix + permanent sync

• server.json was advertising 2.7.3 / "38 tools" on the MCP registry while npm was on 2.13.0 / 42 tools. Now synced.
• npm version runs scripts/sync-manifests.mjs (+ prettier) so server.json + manifest.json bump in the same commit as package.json.
• New manifests.test.ts fails CI if the three ever diverge again.

MCPB bundle — one-click Claude Desktop install

• New manifest.json (validated with mcpb validate) + .mcpbignore.
• Publish workflow packs coolify-mcp.mcpb (prod-only node_modules, ~3 MB) and attaches it to every GitHub release.
• README: drag-into-Settings→Extensions install section with a stable releases/latest/download link.

MCP Registry auto-publish

• Publish workflow pushes server.json to registry.modelcontextprotocol.io via mcp-publisher (GitHub OIDC, retries for npm propagation lag) after each release — the listing can't go stale again.

Verification

• npm test: 410/410 pass (3 new tests)
• npm run lint / npm run build: clean (12 pre-existing warnings untouched)
• mcpb validate manifest.json: passes
• Packed a bundle with the exact CI recipe, unpacked it, and booted it: answers MCP initialize with coolify 2.13.0 — src/docs correctly excluded, 2144 files / 9.3 MB unpacked
• Note: the registry-publish CI step can only be truly exercised on the next real release

🤖 Generated with Claude Code