docs(readme): launch refresh — new screenshots + copy aligned with the blog post

Replace the README screenshot set with the staged Honeycomb Studios
assets from the launch blog post. The previous hero showed a real
internal community (internal channel names, employee avatars, and an
in-flight auth-boundary discussion) and predated the forge UI.

- Hero: engineering channel — humans and agents sharing code, test
  results, and a release decision
- Gallery: agent swarm coordination + Git forge PR view (new),
  media comments retained; agent-member and create-channel shots removed
- Copy: lead with the coordination thesis; 'authorization does not
  erase authorship' in the agent bullet; Git bullet now separates what
  ships today (hosting + early forge UI) from branches-as-rooms
- Status table: forge UI, huddles, and Buzz Mesh added to works-today;
  push notifications moved to being-wired-up (gateway shipped in #1770)
- Fix stale 'four vision docs' (there are seven); link buzz.xyz;
  one architecture sentence on CAS packfiles + TLA+-checked pointer swap
- seed-admin-dashboard.sh: repoint fixtures at the new image files

Co-authored-by: Tyler Longwell <tlongwell@block.xyz>
Signed-off-by: Tyler Longwell <tlongwell@block.xyz>

README.md

@@ -14,18 +14,20 @@
 </p>
 
 <p align="center">
-  <img src="docs/assets/screenshots/channel-thread.png" alt="A Buzz channel with a thread open — a human and an agent working through a question together" width="100%">
+  <img src="docs/assets/screenshots/engineering-channel.png" alt="A Buzz engineering channel where people and agents share code, test results, an issue link, and a release decision" width="100%">
 </p>
 
 <p align="center">
-  <sub><em>A human and an agent working a question in the same thread.</em></sub>
+  <sub><em>The conversation with the code in it — humans and agents in the same channel.</em></sub>
 </p>
 
 ---
 
 ## What is this, really?
 
-Buzz is a self-hostable workspace where humans and AI agents share the same rooms.
+Models can do the work now. Teams still need somewhere to do it together. The bottleneck moved from intelligence to coordination.
+
+Buzz is a self-hostable workspace where humans and AI agents share the same rooms — where people, agents, repos, and decisions work in one place, and a project becomes a conversation with code in it.
 
 A Buzz **community** is the workspace a user reaches by URL. In the single-relay
 setup that ships today, the relay URL selects exactly one community. A hosted
@@ -44,8 +46,8 @@ Yes, it's another AI-adjacent developer tool. We're sorry. The difference is wha
 ## Stuff you do in Buzz
 
 - **Ask the project a question and get an answer with receipts.** Agents search six months of history and post the threads, not vibes.
-- **Let an agent triage a bug without giving it the keys to the kingdom.** Agents have their own keys, their own channel memberships, and their own audit trail. Scoped by identity, not by permission flags — the same way you'd scope a teammate.
-- **Turn a feature branch into a room** where patches, CI, review, and the merge decision live together — so the channel becomes the record of why the code exists.
+- **Let an agent triage a bug without giving it the keys to the kingdom.** Agents have their own keys, their own channel memberships, and their own audit trail. Authorization does not erase authorship: the owner signs a scoped authorization, and the agent signs its own work — scoped by identity, the same way you'd scope a teammate.
+- **Host and review Git work beside the conversation.** Git hosting and an early forge UI ship today — repos, PRs, review. Branches-as-rooms, where patches, CI, and the merge decision share a channel, is the next layer.
 - **Search the conversation, the patch, the workflow run, and the approval in one place** — because they're all the same kind of event.
 - **Let an agent run the workspace, not just talk in it.** Channels, canvases, workflows, huddles — agents have the same surface area as humans, with their own keys and their own audit trail.
 
@@ -56,12 +58,12 @@ Yes, it's another AI-adjacent developer tool. We're sorry. The difference is wha
 <table>
   <tr>
     <td width="50%" valign="top">
-      <img src="docs/assets/screenshots/channel-agents.png" alt="A channel with an agent added as a member, alongside Create agent and Add people cards" width="100%"><br>
-      <sub><strong>Agents are members, not bots.</strong> Add an agent to a channel the same way you add a person.</sub>
+      <img src="docs/assets/screenshots/agent-swarm.png" alt="Buzz agents delegating implementation and deployment work, reviewing pull requests, and returning the final decision to a human" width="100%"><br>
+      <sub><strong>Agents coordinate in the room.</strong> They delegate, open work, review each other — and return the decision to a human.</sub>
     </td>
     <td width="50%" valign="top">
-      <img src="docs/assets/screenshots/create-channel.png" alt="The Create a new channel dialog with name, description, and a private toggle" width="100%"><br>
-      <sub><strong>Spin up a room in seconds.</strong> Name it, describe it, make it private.</sub>
+      <img src="docs/assets/screenshots/forge-pull-request.png" alt="The Buzz Git forge showing a pull request with review status, branches, activity, and comments" width="100%"><br>
+      <sub><strong>Git lives beside the conversation.</strong> Repos, PRs, review state, and comments stay in Buzz.</sub>
     </td>
   </tr>
   <tr>
@@ -99,11 +101,13 @@ Agents are part of the room, not haunted cron jobs.
 | ✅ Works today | 🚧 Being wired up | 💭 Strong opinions, pending code |
 |---|---|---|
 | Relay, channels, threads, DMs, canvases, media, search, audit log | Mobile clients (iOS + Android, Flutter) | Web-of-trust reputation across relays |
-| Desktop app (Tauri + React) | Workflow approval gates (infra exists, glue still drying) | Push notifications |
-| `buzz-cli` (agent-first, JSON in / JSON out) + ACP harness (Goose, Codex, Claude Code) | Huddle lifecycle events | Culture features |
-| YAML workflows: message / reaction / schedule / webhook triggers | | |
+| Desktop app (Tauri + React) | Workflow approval gates (infra exists, glue still drying) | Culture features |
+| `buzz-cli` (agent-first, JSON in / JSON out) + ACP harness (Goose, Codex, Claude Code) | Push notifications (gateway shipped, delivery pipeline in progress) | |
+| YAML workflows: message / reaction / schedule / webhook triggers | Branches-as-rooms and the full merge workflow | |
 | Git events (NIP-34: patches, repo announcements, status) | | |
-| Git hosting backend | | |
+| Git hosting + an early forge UI (repos, PRs, review) | | |
+| Huddles — voice relay + lifecycle events | | |
+| Buzz Mesh — community-gated shared AI compute (opt-in build) | | |
 
 <sub>Please do not plan your compliance program around the 💭 column yet. The <a href="VISION.md">VISION docs</a> are the long version of what we think this becomes.</sub>
 
@@ -195,7 +199,7 @@ If you'd rather point buzz at a different bash-compatible shell, set `BUZZ_SHELL
  └──────────────┘
 ```
 
-A Rust workspace of focused crates. Single source of truth: the relay. See [ARCHITECTURE.md](ARCHITECTURE.md) for the full breakdown.
+A Rust workspace of focused crates. Single source of truth: the relay. Git repos live on object storage as immutable, content-addressed packfiles plus one mutable manifest pointer advanced by compare-and-swap — the storage protocol is specified in TLA+ and model-checked for durability, reconstruction, and concurrent pushes. See [ARCHITECTURE.md](ARCHITECTURE.md) for the full breakdown.
 
 <details>
 <summary><strong>Crate map</strong></summary>
@@ -218,7 +222,7 @@ A Rust workspace of focused crates. Single source of truth: the relay. See [ARCH
 
 ## Going further
 
-- **[VISION.md](VISION.md)** · **[VISION_SOVEREIGN.md](VISION_SOVEREIGN.md)** · **[VISION_PROJECTS.md](VISION_PROJECTS.md)** · **[VISION_AGENT.md](VISION_AGENT.md)** — the four vision docs
+- **[VISION.md](VISION.md)** · **[VISION_SOVEREIGN.md](VISION_SOVEREIGN.md)** · **[VISION_PROJECTS.md](VISION_PROJECTS.md)** · **[VISION_AGENT.md](VISION_AGENT.md)** · **[VISION_ACTIVITY.md](VISION_ACTIVITY.md)** · **[VISION_MESH.md](VISION_MESH.md)** · **[VISION_MODERATION.md](VISION_MODERATION.md)** — the vision docs
 - **[ARCHITECTURE.md](ARCHITECTURE.md)** — system design, kind ranges, subsystem boundaries
 - **[TESTING.md](TESTING.md)** — multi-agent E2E test suite
 - **[CONTRIBUTING.md](CONTRIBUTING.md)** · **[CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)** · **[SECURITY.md](SECURITY.md)** · **[GOVERNANCE.md](GOVERNANCE.md)**
@@ -260,6 +264,6 @@ just reset          # ⚠️  Wipe data + recreate
 ---
 
 <p align="center">
-  <sub>Buzz 🐝</sub><br>
+  <sub><a href="https://buzz.xyz">buzz.xyz</a> · Buzz 🐝</sub><br>
   <sub>Apache 2.0 · Built by <a href="https://block.xyz">Block, Inc.</a></sub>
 </p>

scripts/seed-admin-dashboard.sh

@@ -78,8 +78,8 @@ upload_fixture() {
 
 fixture_dir="$(mktemp -d "${TMPDIR:-/tmp}/buzz-admin-feedback.XXXXXX")"
 search_image="${REPO_ROOT}/docs/assets/screenshots/media-comments.png"
-workspace_image="${REPO_ROOT}/docs/assets/screenshots/channel-thread.png"
-quality_image="${REPO_ROOT}/docs/assets/screenshots/channel-agents.png"
+workspace_image="${REPO_ROOT}/docs/assets/screenshots/engineering-channel.png"
+quality_image="${REPO_ROOT}/docs/assets/screenshots/agent-swarm.png"
 composer_diagnostics="${fixture_dir}/composer-diagnostics.txt"
 workspace_diagnostics="${fixture_dir}/workspace-diagnostics.txt"
 trap 'rm -f "${composer_diagnostics}" "${workspace_diagnostics}"; rmdir "${fixture_dir}"' EXIT