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

[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.6.9) — a Rust-based autonomous AI assistant — following the standard Dokploy template structure. The docker-compose.yml and template.toml are well-formed, the meta.json entry is complete and correctly versioned, and the removed Strapi block was a duplicate (the canonical entry is preserved).

Confidence Score: 5/5

Safe to merge; all remaining findings are minor style suggestions.

Both new files follow AGENTS.md conventions (version 3.8, expose not ports, restart policy, pinned image, named volume). The only findings are P2: PNG logo instead of preferred SVG, and PROVIDER not exposed as a configurable template variable. Neither affects correctness or deployment reliability.

No files require special attention.

Vulnerabilities

No security concerns identified. The API_KEY is auto-generated using Dokploy's ${password:64} helper (not hardcoded). Docker image is pinned to a specific version (0.6.9). ZEROCLAW_ALLOW_PUBLIC_BIND=true is intentional and appropriate given that Dokploy's reverse proxy handles external exposure.

Comments Outside Diff (1)

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

   PNG logo instead of preferred SVG

   The AGENTS.md style guide specifies "SVG preferred, ~128x128px" for blueprint logos. The submitted logo is a .png file. This isn't a hard blocker, but converting or providing an SVG version would align with the project's stated convention and typically yields a sharper result in the UI at any scale.

   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 1 inline comment on this PR.

_{(5/5) You can turn off certain types of comments like style here!}

Context used:

• Context used - AGENTS.md (source)

[greptile-apps]

PROVIDER not user-configurable via template

The docker-compose.yml exposes PROVIDER with a shell default (${PROVIDER:-openrouter}), implying it can be overridden. However, template.toml hardcodes it as "PROVIDER=openrouter" with no corresponding [variables] entry, so users deploying through Dokploy's template importer cannot set a different provider at deploy time without manually editing the Compose file. If multi-provider support is a feature of ZeroClaw, consider promoting this to a template variable in [variables] with a default of openrouter.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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