feat: add/update ZeroClaw template (v0.7.0-beta.1040)

[theonlyhennygod]

Summary

• Adds/updates ZeroClaw template to v${VERSION}
• Image: ghcr.io/zeroclaw-labs/zeroclaw:${VERSION}
• ZeroClaw is a fast, small, fully autonomous AI personal assistant (100% Rust)
• Multi-arch: linux/amd64 + linux/arm64

Checklist

• Read README.md suggestions
• Tested template in personal Dokploy instance
• Confirmed all requirements met

Testing

• Deployed via Compose service import
• Service starts and gateway is accessible on port 42617
• Health check passes

Links

• https://github.com/zeroclaw-labs/zeroclaw
• https://github.com/orgs/zeroclaw-labs/packages/container/package/zeroclaw

Greptile Summary

This PR adds the ZeroClaw (v0.7.0-beta.1040) template — a self-hosted, Rust-based autonomous AI assistant. The blueprint structure, docker-compose.yml, and meta.json entry are all correct, and the Strapi removal visible in the diff is the deduplication script legitimately removing a pre-existing duplicate entry.

• P1 — API_KEY is the LLM provider credential, not a gateway key. Per ZeroClaw's official environment variable docs, API_KEY is the "Primary provider API key." Setting it to ${password:64} (a random 64-char string) causes the service to start and pass health checks, but every AI call will fail with an authentication error from the provider. The user's real OpenRouter (or other provider) API key must be supplied — it should not be auto-generated.

Confidence Score: 4/5

Mergeable after fixing the API_KEY variable — as-is the service boots but all AI functionality is broken.

One P1 finding: auto-generating the primary LLM provider API key as a random password means any deployment from this template will start but be non-functional for AI tasks. The rest of the blueprint follows all Dokploy conventions correctly.

blueprints/zeroclaw/template.toml — api_key variable definition needs to accept user-provided value instead of auto-generating.

Comments Outside Diff (1)

1. blueprints/zeroclaw/zeroclaw.png, line 1 (link)

   PNG logo instead of preferred SVG format

   The project guidelines specify "SVG preferred, ~128x128px" for template logos. Using PNG works, but an SVG would scale cleanly at all resolutions in the Dokploy UI.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

_{Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.7..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	7311e39

[greptile-apps]

API_KEY auto-generated but must be the user's provider API key

According to the official ZeroClaw environment variable docs, API_KEY is the "Primary provider API key" used to authenticate with the chosen LLM provider (OpenRouter by default). Generating it as ${password:64} produces a random string that will be rejected by OpenRouter, so the deployed service can start but cannot make any AI calls. The user's real provider API key must be supplied here — it should not be auto-generated.

Suggested change

	api_key = "${password:64}"
	api_key = ""

Consider leaving it as a plain empty variable so that Dokploy prompts the user to enter their actual OpenRouter (or other provider) API key before the service is usable.