#11415: Update package.json metadata for npm discoverability

## Summary - **Update `description`** — was still "WhatsApp gateway CLI (Baileys web) with Pi RPC agent", now reflects what OpenClaw actually is - **Add `keywords`** — empty array meant the package was harder to find on npm - **Add missing npm metadata** — `author`, `homepage`, `repository`, `bugs` fields - **Remove duplicate vitest exclude** — `apps/macos/.build/**` was listed twice - **Fix grammar** — "a OpenClaw" → "an OpenClaw" in `docs/start/showcase.md` ## Test plan - [x] No code logic changes — metadata and docs only - [x] Verified JSON is valid 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates root `package.json` npm metadata (description, keywords, author, homepage, repository, bugs) to better reflect OpenClaw and improve npm discoverability, and removes a duplicated vitest exclude entry. It also makes a small grammar fix in `docs/start/showcase.md` ("a" → "an"). Changes are isolated to documentation and package metadata and follow existing repository conventions for npm fields (e.g., `repository`/`bugs` object shapes). <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk. - Changes are limited to documentation text and npm metadata fields in package.json; JSON structure remains valid and new metadata matches established repo conventions. No runtime logic or build configuration semantics were altered beyond removing a duplicate exclude entry. - No files require special attention <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} <!-- /greptile_comment -->