docs: note ZeroClaw as alternate runtime in spec §12

The spec is runtime-agnostic — what matters is conformant events per
§4 and community scoping per §5. Adopters who want a richer agent
layer than a focused Matrix bot can satisfy the spec on top of
ZeroClaw (Rust, Apache/MIT, ships Matrix + Nostr channels + Ollama
provider). Renderers filter by community a-tag, not by client tag,
so multi-runtime ecosystems work without coordination.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/community-organizer-spec.md

@@ -635,6 +635,19 @@ to drive a 13.3" panel in the community's shared foyer.
 
 Both serve as worked examples of the spec; neither is mandatory.
 
+### Alternate runtimes
+
+Adopters who want a richer agent layer than a focused Matrix bot can
+satisfy this spec on top of a general-purpose agent runtime such as
+[ZeroClaw](https://github.com/zeroclaw-labs/zeroclaw) (Rust, Apache-2.0
+/ MIT, ships Matrix + Nostr channels and Ollama provider out of the
+box). The spec is runtime-agnostic — what matters is that captured
+input produces conformant events per §4 and respects the community
+scoping in §5. A ZeroClaw-based implementation would carry the
+`["client", "zeroclaw", "<version>"]` tag (per §4.1) instead of
+`["client", "maubot-tracker", "..."]`; renderers ignore the difference
+since they filter by community `a`-tag.
+
 ---
 
 ## Changelog