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

[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.6.7) — a Rust-based AI personal assistant — to the Dokploy template registry. The docker-compose.yml is well-structured and follows all repository conventions. However, two issues need to be addressed before merging:

• Accidental Strapi removal: The strapi entry was deleted from meta.json even though its blueprint folder (blueprints/strapi/) still exists. This is unrelated to the ZeroClaw addition and appears to be an accidental side-effect, likely from a merge conflict resolution or running the sort script against a dirty tree. Restoring it is required.
• AI provider key generated as random password: template.toml uses ${password:64} to auto-generate the API_KEY, but this variable holds the user's upstream AI provider credential (OpenRouter, OpenAI, etc.). A randomly generated value will never authenticate with any provider, leaving the service non-functional out of the box. It should be left empty, consistent with how other AI templates in this repo handle user-supplied provider keys.
• Logo format: PNG is used instead of the SVG format recommended by AGENTS.md — minor/optional improvement.

Confidence Score: 4/5

Two P1 issues must be resolved before merging: the accidental Strapi deletion from meta.json and the misconfigured AI provider API key.

The docker-compose.yml is solid and follows all conventions. The two P1 issues — unintentional removal of an existing template entry and an auto-generated value for a user-supplied credential — prevent the PR from being merge-ready as-is.

meta.json (Strapi entry deletion) and blueprints/zeroclaw/template.toml (API_KEY auto-generation)

Important Files Changed

Filename	Overview
blueprints/zeroclaw/docker-compose.yml	Well-formed compose file: correct version, uses expose not ports, includes restart: unless-stopped, named volume, image pinned to 0.6.7. No issues.
blueprints/zeroclaw/template.toml	Domain and port wiring are correct, but api_key = "${password:64}" auto-generates a random credential for the upstream AI provider key — this value will never authenticate with OpenRouter/OpenAI and will cause the service to be non-functional on first deploy.
meta.json	ZeroClaw entry added correctly (id, version, logo, tags all consistent), but the existing strapi entry was accidentally removed — its blueprint folder still exists in the repo.
blueprints/zeroclaw/zeroclaw.png	Logo file present and referenced correctly in meta.json; PNG instead of the preferred SVG format per AGENTS.md, but functional.

Comments Outside Diff (1)

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

   Accidental Strapi entry removal

   The strapi entry has been deleted from meta.json, but its blueprint (blueprints/strapi/) is still present in the repository. This removal is unrelated to the ZeroClaw addition and appears to be unintentional — likely a merge conflict artifact or a side-effect of running the dedup/sort script after a conflict. Without this entry, Strapi will no longer appear in the template registry even though the underlying compose files are intact.

   Please restore the Strapi entry and re-run npm run process-meta to ensure the registry is sorted correctly before merging.

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

Greptile also left 2 inline comments on this PR.

_{(4/5) You can add custom instructions or style guidelines for the agent here!}

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	6873dbc

[greptile-apps]

api_key auto-generation will produce an unusable value

${password:64} generates a random 64-character string and injects it as the API_KEY for the upstream AI provider (OpenRouter, OpenAI, etc.). A randomly generated value is not a valid credential for any AI provider, so the service will fail to make AI requests after deployment.

This variable represents a user-supplied provider credential, not an internal application secret. The correct pattern (used by other AI templates in this repo such as blueprints/anse/template.toml) is to leave the value empty so users are prompted to fill in their real provider key after deployment. The api_key variable definition and its ${password:64} helper should be removed, and API_KEY in the env array should be left blank.

[greptile-apps]

Logo format: PNG used instead of preferred SVG

AGENTS.md states "SVG preferred, ~128x128px" for logo files. The template uses zeroclaw.png, which is a raster format. While PNG will work, SVG scales cleanly at any size and is the preferred format across the repository. If an SVG version of the logo is available, swapping it in would keep the project consistent.

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!}