Rename project: too many repos named "ClawWork" on GitHub

## Problem

Searching "clawwork" on GitHub returns 10+ repositories with the same or very similar names, including a highly active one (`HKUDS/ClawWork` — "OpenClaw as Your AI Coworker"). This causes:

- **SEO confusion**: hard to find us in search results
- **Brand ambiguity**: users can't tell which project is which
- **Package/Homebrew namespace conflicts**: potential collisions in package registries

## Current Name Collision (top results)

| Repo | Description | Activity |
|---|---|---|
| **HKUDS/ClawWork** | "OpenClaw as Your AI Coworker — $15K earned in 11 Hours" | Very active |
| **clawwork-ai/ClawWork** | ← Us | Active |
| clawplaza/clawwork-cli | CLI tool | Recent |
| lorenzopapa2/clawwork | AI Agent Social Collaboration Marketplace | Recent |
| + 6 others | Various forks/projects | — |

## Action Items

- [ ] Brainstorm new project name (unique, memorable, related to OpenClaw desktop client)
- [ ] Check availability: GitHub org, npm, Homebrew, domain
- [ ] Rename GitHub org + repo
- [ ] Update all references: package.json, README, CLAUDE.md, Homebrew cask, release workflows, etc.
- [ ] Set up redirect from old repo

## Naming Constraints

- Should clearly convey: **desktop client for OpenClaw**
- Unique enough to avoid future collisions
- Short, easy to type and remember
- Works as a CLI command name if needed

Start by reviewing the naming constraints and the references listed in package.json, README, CLAUDE.md, the Homebrew cask, and release workflows. Check availability across GitHub, npm, Homebrew, and the domain before selecting a unique name. Done means the project is renamed, references are updated, and a redirect from the old repository is set up.

Written by the indexing model from the issue text.