feat: add/update ZeroClaw template (v0.7.3-beta.1051)

[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 a new ZeroClaw blueprint (v0.7.3-beta.1051) with a docker-compose, template.toml, logo, and meta.json entry. Two blocking issues exist: the Strapi entry has been accidentally deleted from meta.json (its blueprint files are still present), and the API_KEY for the LLM provider is populated with an auto-generated random string rather than a real user-supplied provider credential, which will cause the service to fail on first use.

Confidence Score: 3/5

Not safe to merge — accidental Strapi removal breaks an existing template, and the API_KEY misconfiguration will cause ZeroClaw to fail on first use.

Two P1 issues are present: the unintended removal of the Strapi registry entry (which breaks an existing template for all users) and the incorrect use of a generated password as the user's external LLM provider API key. Both need to be fixed before this can be merged.

meta.json (Strapi removal) and blueprints/zeroclaw/template.toml (API_KEY generation)

Comments Outside Diff (2)

1. meta.json, line 5952-5969 (link)

   Strapi entry unintentionally removed

   The strapi entry has been deleted from meta.json, but blueprints/strapi/ (with docker-compose.yml, template.toml, strapi.svg) still exists on disk. Removing it from the registry makes Strapi invisible in the Dokploy template browser while its blueprint files remain, leaving it in a broken/orphaned state. This change is not mentioned in the PR description and appears accidental — likely caused by a merge conflict or a stale meta.json base. The entry should be restored.

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

   PNG logo — SVG preferred

   Per project conventions, logo files should be SVG (~128×128 px) for sharper rendering at all sizes. PNG will work but is not the preferred format. If an SVG source is available, swapping it in would be better.

   Context Used: AGENTS.md (source)

   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	3c8b750

[greptile-apps]

API_KEY auto-generated instead of user-supplied

The api_key variable is populated with a randomly generated 64-character string via the password helper, but it is paired with PROVIDER=openrouter in the env block — indicating it is the credential for an external LLM provider (OpenRouter, etc.), not a local gateway secret. A randomly generated value cannot authenticate against any real AI provider, so the deployment will fail at runtime until the user manually replaces it. Consider leaving the variable empty and requiring the user to enter their own key, or at minimum adding a comment that the value must be overridden post-deploy.