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

[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 template (v0.7.1-beta.1049) with a docker-compose.yml, template.toml, logo, and meta.json entry. However, it also unintentionally removes the existing Strapi entry from meta.json while Strapi's blueprint files remain on disk, and the API_KEY variable is auto-generated rather than accepting user input, which will likely break LLM provider authentication on every deployment.

• Strapi removed from meta.json — blueprints/strapi/ still exists; the registry entry must be restored.
• API_KEY auto-generated — with PROVIDER=openrouter, this is almost certainly an external provider credential that must be supplied by the user, not randomly generated.

Confidence Score: 3/5

Not safe to merge — removes an existing template from the registry and likely ships a non-functional API key configuration.

Two P1 issues: the Strapi entry is silently dropped from meta.json (orphaning its blueprint files), and the auto-generated API_KEY will break LLM provider authentication for every ZeroClaw deployment. Both must be resolved 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 Strapi template entry is deleted from meta.json, but its blueprint files (blueprints/strapi/docker-compose.yml, template.toml, strapi.svg) still exist. This leaves Strapi's compose files orphaned and invisible in the template registry. This looks like an accidental side-effect — likely caused by running dedupe-and-sort-meta.js in a state where Strapi was already absent, or a merge conflict resolution that dropped the block. The Strapi entry should be restored.

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

   SVG preferred over PNG for logo

   Per project conventions, logo files should be SVG (~128×128 px) for crisp rendering at all sizes. A PNG will work but may appear blurry in the UI at higher DPI. Consider providing an SVG version.

   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	820205a

[greptile-apps]

Random value used for what may be an external LLM provider key

The template auto-generates a random 64-character string for api_key and injects it as API_KEY. Since PROVIDER is set to openrouter, this variable is almost certainly the user's LLM provider credential — a value only the user possesses. Deploying with a randomly-generated value will cause every instance to fail provider authentication silently. If API_KEY is instead ZeroClaw's own internal gateway token (unrelated to the upstream provider), please clarify this in a comment; otherwise the template should prompt the user to supply their own value rather than auto-generating one.