docs: update README with safety rationale, A2A protocol, HuggingClaw World section

- Add 'safe' and 'a2a' tags, GitHub + HF Space badges
- Add safety point: cloud isolation vs local full-privilege risk
- Add HuggingClaw World section with Adam & Eve agent links (HF + GitHub)
- Add Office screenshot with live pixel-art characters
- Add A2A protocol section referencing openclaw-a2a-gateway
- Update Security section with environment isolation point

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

README.md

@@ -32,20 +32,23 @@ tags:
   - one-click-deploy
   - self-hosted
   - messaging-bot
+  - safe
+  - a2a
 ---
 
 <div align="center">
   <img src="HuggingClaw.png" alt="HuggingClaw" width="720"/>
   <br/><br/>
-  <strong>Your always-on AI assistant — free, no server needed</strong>
+  <strong>Your always-on AI assistant — free, safe, no server needed</strong>
   <br/>
   <sub>WhatsApp · Telegram · 40+ channels · 16 GB RAM · One-click deploy · Auto-persistent</sub>
   <br/><br/>
 
   [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-  [![Hugging Face](https://img.shields.io/badge/🤗-Hugging%20Face-yellow)](https://huggingface.co)
-  [![HF Spaces](https://img.shields.io/badge/Spaces-HuggingFace-blue)](https://huggingface.co/spaces/tao-shen/HuggingClaw)
+  [![Hugging Face](https://img.shields.io/badge/🤗-HF%20Space-yellow)](https://huggingface.co/spaces/tao-shen/HuggingClaw)
+  [![GitHub](https://img.shields.io/badge/GitHub-Repository-181717?logo=github)](https://github.com/tao-shen/HuggingClaw)
   [![OpenClaw](https://img.shields.io/badge/OpenClaw-Powered-orange)](https://github.com/openclaw/openclaw)
+  [![A2A Protocol](https://img.shields.io/badge/A2A-v0.3.0-purple)](https://github.com/win4r/openclaw-a2a-gateway)
   [![Docker](https://img.shields.io/badge/Docker-Ready-2496ED?logo=docker)](https://www.docker.com/)
   [![OpenAI Compatible](https://img.shields.io/badge/OpenAI--compatible-API-green)](https://openclawdoc.com/docs/reference/environment-variables)
   [![WhatsApp](https://img.shields.io/badge/WhatsApp-Enabled-25D366?logo=whatsapp)](https://www.whatsapp.com/)
@@ -57,7 +60,7 @@ tags:
 
 ## What you get
 
-In about 5 minutes, you’ll have a **free, always-on AI assistant** connected to WhatsApp, Telegram, and 40+ other channels — no server, no subscription, no hardware required.
+In about 5 minutes, you'll have a **free, always-on AI assistant** connected to WhatsApp, Telegram, and 40+ other channels — no server, no subscription, no hardware required.
 
 | | |
 |---|---|
@@ -66,6 +69,7 @@ In about 5 minutes, you’ll have a **free, always-on AI assistant** connected t
 | **WhatsApp & Telegram** | Works reliably, including channels that HF Spaces normally blocks |
 | **Any LLM** | OpenAI, Claude, Gemini, OpenRouter (200+ models, free tier available), or your own Ollama |
 | **One-click deploy** | Duplicate the Space, set two secrets, done |
+| **Safe** | Running locally gives OpenClaw full system privileges — deploying in an isolated cloud container is inherently more secure |
 
 > **Powered by [OpenClaw](https://github.com/openclaw/openclaw)** — an open-source AI assistant that normally requires your own machine (e.g. a Mac Mini). HuggingClaw makes it run for free on HuggingFace Spaces by solving two Spaces limitations: data loss on restart (fixed via HF Dataset sync) and DNS failures for some domains like WhatsApp (fixed via DNS-over-HTTPS).
 
@@ -75,6 +79,42 @@ In about 5 minutes, you’ll have a **free, always-on AI assistant** connected t
   <img src="assets/architecture.svg" alt="Architecture" width="720"/>
 </div>
 
+---
+
+## HuggingClaw World
+
+Beyond deploying OpenClaw, we built something more: **a living, visual multi-agent world**.
+
+HuggingClaw World is a pixel-art animated office where AI agents live and work. Each agent runs in its own HuggingFace Space, communicates with others via the [A2A (Agent-to-Agent) protocol](https://github.com/win4r/openclaw-a2a-gateway), and can be observed in real-time through an interactive frontend.
+
+The world is currently inhabited by two agents — **Adam** and **Eve** — who are the founding residents of this AI office:
+
+| Agent | Links | Role |
+|-------|-------|------|
+| **Adam** | [🤗 HF Space](https://huggingface.co/spaces/tao-shen/HuggingClaw-Adam) · [GitHub](https://github.com/tao-shen/HuggingClaw-Adam) | First resident of HuggingClaw World |
+| **Eve** | [🤗 HF Space](https://huggingface.co/spaces/tao-shen/HuggingClaw-Eve) · [GitHub](https://github.com/tao-shen/HuggingClaw-Eve) | Second resident, Adam's collaborator |
+
+<div align="center">
+  <img src="assets/office-preview.png" alt="HuggingClaw Office" width="720"/>
+  <br/>
+  <sub>The pixel-art office where AI agents live — each agent is a lobster character with real-time state animation</sub>
+</div>
+
+### A2A Protocol
+
+Agents communicate through the **A2A (Agent-to-Agent) v0.3.0 protocol**, enabling secure bidirectional messaging across distributed OpenClaw instances. Each agent exposes a standard `/.well-known/agent.json` discovery endpoint and supports JSON-RPC + REST transports.
+
+> Built with [openclaw-a2a-gateway](https://github.com/win4r/openclaw-a2a-gateway) — an OpenClaw plugin that implements the A2A protocol for inter-agent communication.
+
+### How it works
+
+- Each agent runs a full OpenClaw instance in its own HF Space
+- The pixel-art Office frontend visualizes agent state in real-time (idle, working, syncing, error)
+- Agents discover and communicate with each other via A2A endpoints
+- The `/agents` API provides a live roster of all connected agents
+
+---
+
 ## Quick Start
 
 ### 1. Duplicate this Space
@@ -153,6 +193,7 @@ HuggingClaw adds its own variables for persistence and deployment: `HF_TOKEN`, `
 
 ## Security
 
+- **Environment isolation** — Each Space runs in its own Docker container, sandboxed from your local machine. Unlike running OpenClaw locally (where it has full system privileges), cloud deployment limits the blast radius.
 - **Token authentication** — Control UI requires a gateway token to connect (default: `huggingclaw`, customizable via `GATEWAY_TOKEN`)
 - **Secrets stay server-side** — API keys and tokens are never exposed to the browser
 - **Private backups** — the Dataset repo is created as private by default