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

[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.6.5 template (a 100% Rust autonomous AI assistant). The blueprint structure is mostly correct — version: "3.8", expose instead of ports, named volume, and restart: unless-stopped all follow the project conventions. However, two blocking issues need to be resolved before merging:

• API_KEY auto-generation (template.toml): The template assigns a randomly-generated 64-character string to API_KEY, which is the user's AI-provider credential (e.g. OpenRouter key). This will cause ZeroClaw to fail authentication with the AI provider immediately on deployment. The field should require the user to supply their own key.
• Accidental Strapi removal (meta.json): The Strapi entry was silently deleted from meta.json even though the blueprints/strapi/ directory (with all blueprint files) still exists. This is almost certainly an unintentional side-effect of a merge conflict and must be restored before this PR lands.

Minor: the logo is PNG rather than the project-preferred SVG format, but this is non-blocking.

Confidence Score: 2/5

Not safe to merge — accidental Strapi removal from meta.json and a broken API_KEY default that prevents ZeroClaw from working need to be fixed first.

Two P1 issues block merge: the Strapi entry deletion is a clear regression for an existing template, and auto-generating the AI-provider API key will produce a non-functional deployment out-of-the-box. Both are straightforward to fix but must be addressed.

blueprints/zeroclaw/template.toml (api_key default) and meta.json (Strapi removal)

Important Files Changed

Filename	Overview
blueprints/zeroclaw/docker-compose.yml	New compose file is structurally correct — version 3.8, uses expose not ports, has restart: unless-stopped, named volume, service name matches blueprint folder.
blueprints/zeroclaw/template.toml	Auto-generates api_key with a random password helper, but API_KEY is the user's AI-provider credential — the service will fail to authenticate out-of-the-box.
meta.json	Adds ZeroClaw entry correctly, but unexpectedly removes the Strapi entry even though the blueprint directory still exists — likely an accidental merge conflict artifact.
blueprints/zeroclaw/zeroclaw.png	Logo PNG added. SVG is preferred per project guidelines but PNG is functional.

Comments Outside Diff (1)

1. blueprints/zeroclaw/zeroclaw.png

   Logo format: PNG instead of preferred SVG

   Per the project's AGENTS.md style guide, SVG is the preferred logo format (~128×128 px). PNG will work but lacks the resolution-independence of SVG. If a vector version of the ZeroClaw logo is available, swapping to .svg would be preferable.

   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.6..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

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	6ab1588

[greptile-apps]

API_KEY should not be auto-generated

API_KEY in this template is the user's AI-provider credential (e.g. their OpenRouter API key), not an internal application secret. Auto-generating it with the ${password:64} helper will produce a random string that is not a valid OpenRouter key, so ZeroClaw will fail to authenticate with the AI provider immediately after deployment.

The variable should be left without a generated default so that Dokploy prompts the user to supply their own key. Consider replacing the auto-generated value with an empty placeholder and adding a comment in the TOML (or a short README) making clear that users must paste in their own provider key before deploying.

[greptile-apps]

Strapi entry unexpectedly removed from meta.json

This PR removes the strapi entry from meta.json, but the PR description only mentions adding/updating ZeroClaw. The blueprints/strapi/ directory (with docker-compose.yml, template.toml, and strapi.svg) still exists in the repository, so this appears to be an accidental deletion — likely a bad merge conflict resolution.

Strapi is a widely-used headless CMS and its template should not disappear from the index. Please restore the removed block and then run npm run process-meta to re-sort the file so CI validation passes.