feat(scripts): add mesh registry publish scripts

[JonasJesus42]

Add publish-one.ts for CI workflow (single MCP) and publish-all.ts for bulk publishing to the Mesh Admin registry. Integrates into the deploy workflow so each MCP is published to both Deco CLI and Mesh Registry on deploy.

---

Summary by cubic

Adds Mesh Registry publish to the deploy pipeline so each MCP is published to both Deco CLI and Mesh Registry on deploy. Improves bulk publisher resilience and correctness for unlisted apps.

• New Features

  • scripts/publish-one.ts: CI single MCP publisher; builds from app.json + README; uses last git committer; supports --dry-run and MESH_ADMIN_URL override.
  • scripts/publish-all.ts: Bulk local publisher; scans MCPs with app.json; supports --dry-run, --filter, --delay, --max-retries, --resume/--reset; retries 429s with 60s backoff and saves progress; defaults to production Mesh Admin URL.
  • CI: deploy.yml runs “Publish (Mesh Registry)” after the Deco CLI deploy step.
  • Payload maps app metadata (verified, tags/categories, tools, icon, remote URL) to Mesh Registry fields.

• Bug Fixes

  • Respect metadata.mesh_unlisted as a fallback for is_public in both scripts.
  • Handle network errors in publish-all with try/catch so the bulk run continues with retries and progress tracking.

^{Written for commit f38b3e0. Summary will update on new commits.}

[cubic-dev-ai]

3 issues found across 3 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/publish-one.ts">

<violation number="1" location="scripts/publish-one.ts:211">
P1: The script ignores the `mesh_unlisted` property from `app.metadata`, which will cause explicitly unlisted apps to be published as public.</violation>
</file>

<file name="scripts/publish-all.ts">

<violation number="1" location="scripts/publish-all.ts:117">
P0: The `PUBLISH_URL` is hardcoded to a local testing endpoint (`localhost:3000`) and will always fail in the CI environment.</violation>

<violation number="2" location="scripts/publish-all.ts:305">
P1: The `fetch` request is missing error handling, causing any network failure to crash the entire bulk publish CI job.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}