feat: add/update ZeroClaw template (v0.7.0-beta.1030)

[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 template (v0.7.0-beta.1030) — a Rust-based AI assistant. The new blueprint files (docker-compose.yml, template.toml, logo) are well-formed and follow repository conventions, but the meta.json diff also removes the existing Strapi template entry, which appears unintentional and would break Strapi availability for all Dokploy users.

• P1: The strapi entry is deleted from meta.json with no explanation. This looks like a merge conflict artifact and should be restored before merging.

Confidence Score: 4/5

Not safe to merge until the accidental Strapi deletion from meta.json is reverted.

The ZeroClaw blueprint itself is correct and complete, but the unintended removal of the Strapi entry from meta.json is a present defect that would silently break an existing well-known template for all users.

meta.json — the Strapi entry deletion must be reverted.

Comments Outside Diff (2)

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

   Unintended removal of Strapi template entry

   The PR removes the entire strapi entry from meta.json (18 lines deleted starting at the original line 5955), but the PR description and title make no mention of removing Strapi. This looks like a merge conflict artifact or accidental deletion. Removing it would make the Strapi template unavailable in the registry for all Dokploy users.

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

   Logo should be SVG (preferred) per project conventions

   The AGENTS.md style guide states "SVG preferred, ~128x128px" for blueprint logos. A PNG will work but an SVG would scale better across different display sizes and is the expected format for this repository.

   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	3558b4a

[greptile-apps]

PROVIDER hardcoded; docker-compose.yml allows override

template.toml hardcodes PROVIDER=openrouter, but docker-compose.yml uses ${PROVIDER:-openrouter} which accepts an env var override. Users deploying through the Dokploy template UI have no way to change the provider. If multi-provider support is intentional, consider exposing PROVIDER as a configurable variable in template.toml.