feat: add/update ZeroClaw template (v0.7.1)

[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.1) for a Rust-based autonomous AI assistant. The compose file and template structure are well-formed and follow conventions, but two issues need attention before merging.

• Strapi removed from meta.json: The diff deletes the entire strapi entry — Strapi's blueprint files still exist but it becomes invisible in the registry. This appears to be an unintended merge/rebase artifact and must be restored.
• API_KEY is auto-generated: ZeroClaw connects to an external AI provider (PROVIDER=openrouter), and API_KEY is almost certainly the user's provider credential. Generating a random value will cause authentication failures at startup; the user should supply their own key.

Confidence Score: 4/5

Not safe to merge until the unintended Strapi removal and the auto-generated API key issue are resolved.

Two P1 findings: the Strapi meta.json entry is silently dropped (breaking that template's discoverability), and the API_KEY is auto-generated in a way that will likely cause ZeroClaw to fail connecting to its AI provider. Both need to be addressed before merging.

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

Comments Outside Diff (2)

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

   Strapi entry unintentionally removed

   The diff removes the entire strapi entry from meta.json but the PR is only meant to add/update ZeroClaw. Strapi's blueprint files still exist in the repository — removing it from meta.json makes it invisible to users of the template registry. This looks like an accidental conflict/rebase artifact and needs to be restored.

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

   SVG preferred over PNG for logo

   AGENTS.md states "Add logo file (SVG preferred, ~128x128px) to blueprint folder." Using a PNG is not a hard blocker, but an SVG would scale better across the Dokploy UI. Consider replacing with an SVG if one is available upstream.

   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.

Context used:

• Context used - AGENTS.md (source)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	2681f82

[greptile-apps]

Auto-generated key may not work as an external provider key

The template generates a random string for api_key (used as API_KEY in the compose env), but ZeroClaw connects to an external AI provider via PROVIDER=openrouter. For AI assistant services the API_KEY is typically the user's own provider credential — an auto-generated random value will cause the service to fail to authenticate with OpenRouter on startup.

If API_KEY is instead an internal gateway auth token (not the LLM provider credential), a comment in the template clarifying this would remove the ambiguity.