docs: quickstart overhaul, ZCP updates, and auto-generated OG images

apps/docs/content/features/coding-agents.mdx

@@ -36,7 +36,7 @@ Most coding-agent platforms went agent-first, then bolted on infrastructure —
 
 ### Your agent, your subscription
 
-Bring whichever agent you already use. Claude Code today; Codex, Gemini CLI, opencode, and any MCP-capable client next. The container is a regular Ubuntu — install your own CLI tools, drop in your `.claude` / `.cursor` configs, attach your IDE over SSH. **Zerops doesn't resell tokens or proxy your model calls** — sign in with your own Anthropic / OpenAI / Google subscription and the agent talks to its provider directly.
+ZCP supports multiple coding agents including Claude Code (Anthropic), Codex (OpenAI), Antigravity, and Grok Build. The container is a regular Ubuntu — install your own CLI tools, drop in your `.claude` / `.cursor` configs, attach your IDE over SSH. **Zerops doesn't resell tokens or proxy your model calls** — sign in with your own Anthropic / OpenAI / Google subscription and the agent talks to its provider directly.
 
 ### An ordinary Zerops project underneath
 
@@ -56,7 +56,7 @@ Runtimes for Bun, Deno, Node.js, Go, Python, Rust, Java, .NET, PHP, Elixir, Glea
 
 The agent reaches your project's private network one of two ways:
 
-- **Remote** — a `zcp` service deployed into the project runs the agent. You attach to it with Claude Code's IDE extension, with any IDE that supports remote development (Cursor, Windsurf, VS Code Remote), or by running [`zcli vpn up`](/references/networking/vpn) and ssh-ing into `zcp` to drive the rest of the project from a shell.
+- **Remote** — a `zcp` service deployed into the project runs the agent. You attach to it with your agent's IDE extension or terminal, with any IDE that supports remote development (Cursor, Windsurf, VS Code Remote), or by running [`zcli vpn up`](/references/networking/vpn) and ssh-ing into `zcp` to drive the rest of the project from a shell.
 - **Local** — install the `zcp` MCP on your machine and run `zcli vpn up` to join the network. From there your IDE, agent, and shell can ssh directly into any container.
 
 Either way, the agent reaches [managed services by hostname](/references/networking/internal-access) (`db:5432`, `cache:6379`), deploys through the [Zerops pipeline](/features/pipeline), and reads logs and events the same way you would.
@@ -173,7 +173,7 @@ With the model clear, here's where ZCP sits among adjacent tools. People say "ag
       <img src="/img/landscape/aider.png" alt="Aider" />
       <img src="/img/landscape/cline.png" alt="Cline" />
     </div>
-    <p className="zcp-landscape-section__examples">Cursor · Windsurf · Zed · Claude Code · Codex CLI · Aider · Cline</p>
+    <p className="zcp-landscape-section__examples">Cursor · Windsurf · Zed · Claude Code · Codex · Antigravity · Grok Build · Aider · Cline</p>
   </header>
   <p>The agent runs on your machine, edits your local checkout, runs local commands. Excellent at code changes. **MCP** is now native across these tools, so external reach — databases, networking, deploy targets, runtime logs — comes through plugins instead of bare hands. The agent still lives on your laptop, though: anything off-machine has to be reached, not *inhabited*. Install the ZCP MCP locally and run `zcli vpn up`, and any of these agents can now reach a real Zerops project alongside your local code: services addressed by hostname, deploys, logs, events.</p>
 </section>
@@ -211,7 +211,7 @@ With the model clear, here's where ZCP sits among adjacent tools. People say "ag
 ## Where to start
 
 <DocCardList items={[
-  { type: 'link', href: '/zcp/quickstart', label: 'Quickstart', customProps: { icon: Icons['rocket-launch'], description: 'AI Agent recipe, Claude Code, and a real product change in about five minutes.' } },
+  { type: 'link', href: '/zcp/quickstart', label: 'Quickstart', customProps: { icon: Icons['rocket-launch'], description: 'AI Agent recipe, bundled coding agent, and a real product change in about five minutes.' } },
   { type: 'link', href: '/zcp/overview', label: 'ZCP MCP overview', customProps: { icon: Icons['sparkles'], description: 'What the `zcp` MCP gives the agent, where it runs, and how a run ends in proof or a blocker.' } },
   { type: 'link', href: '/zcp/setup/choose-workspace', label: 'Remote or local setup', customProps: { icon: Icons['computer-desktop'], description: 'Choose where the `zcp` MCP runs — inside Zerops with bundled tools, or beside your local editor.' } },
   { type: 'link', href: '/zcp/workflows/build-with-zcp', label: 'Build and ship', customProps: { icon: Icons['circle-stack'], description: 'Runtime layout, development, delivery, packaging, and production release.' } },