docs(cloud-agents): scrub private warp-agent-docker links from snapshots docs

The two GitHub URLs the new snapshots page used were both pointing at
warpdotdev/warp-agent-docker, which is a private repo — anonymous
visitors get HTTP 404. Replaced both with link-free user-facing prose
and reworded all text mentions of the internal repo name.

Specifically:

* snapshots.mdx frontmatter description: "bundled warp-agent-docker
  image" → "bundled cloud agent image".
* snapshots.mdx intro paragraph: drop the link to the private repo
  root; refer to "Warp's bundled cloud agent image" instead.
* snapshots.mdx "When to customize" intro: replace "bundled
  warp-agent-docker image" with "bundled cloud agent image".
* snapshots.mdx env-var reference: same swap for
  OZ_SNAPSHOT_DECLARATIONS_SCRIPT description.
* snapshots.mdx "Write a custom declarations script": drop the link
  to the private snapshot-declarations.sh file; the sentence now just
  introduces the minimal pattern.
* snapshots.mdx: add a :::note callout under the script example
  describing what the bundled image's richer implementation does
  beyond the minimal pattern (OZ_SNAPSHOT_SCAN_ROOTS override, jq for
  JSON encoding, dedup against existing repo declarations) so power
  users know what's available without us pointing at private
  artifacts.
* unmanaged.mdx Tracking and observability cross-link: drop the
  "warp-agent-docker" qualifier.

Verified with grep: no more "warp-agent-docker" references anywhere
in src/content/docs/.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: hongyi-chen

src/content/docs/agent-platform/cloud-agents/handoff/snapshots.mdx

@@ -2,19 +2,19 @@
 title: Customizing workspace snapshots
 description: >-
   Customize which repositories and files Warp snapshots at the end of a cloud
-  agent run, so handoff continues to work outside the bundled warp-agent-docker
+  agent run, so handoff continues to work outside the bundled cloud agent
   image.
 sidebar:
   label: "Snapshots"
 ---
 
 Workspace snapshots are how [handoff](/agent-platform/cloud-agents/handoff/) carries repository changes and other workspace state across cloud agent runs. At the end of every cloud agent run, Warp asks a small declarations script which repositories and files to snapshot, then uploads the resulting git diffs and file contents so the next cloud agent run can apply them.
 
-The bundled [`warp-agent-docker`](https://github.com/warpdotdev/warp-agent-docker) image ships with a declarations script that snapshots every git repository under the agent's workspace, so most cloud agent runs need no configuration. This page is for the cases where you need to customize what gets snapshotted — for example, when running cloud agents in a custom Docker image, on a self-hosted [Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/), or as an [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) `oz agent run` in CI.
+Warp's bundled cloud agent image ships with a declarations script that snapshots every git repository under the agent's workspace, so most cloud agent runs need no configuration. This page is for the cases where you need to customize what gets snapshotted — for example, when running cloud agents in a custom Docker image, on a self-hosted [Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/), or as an [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) `oz agent run` in CI.
 
 ## When to customize snapshots
 
-The default snapshotting behavior is sufficient when your cloud agent runs use the bundled `warp-agent-docker` image and operate entirely inside the assigned workspace. Customize snapshots when:
+The default snapshotting behavior is sufficient when your cloud agent runs use the bundled cloud agent image and operate entirely inside the assigned workspace. Customize snapshots when:
 
 * **You use a custom Docker base image** that doesn't include the bundled `snapshot-declarations.sh` script.
 * **You run cloud agents on a self-hosted Direct backend** or as unmanaged `oz agent run` invocations, where the bundled script isn't on disk.
@@ -45,7 +45,7 @@ In both flows, snapshotting is automatically enabled for cloud agent runs when c
 
 ## Environment variables
 
-* **`OZ_SNAPSHOT_DECLARATIONS_SCRIPT`** - Absolute path to the script Warp invokes at the end of each cloud agent run. The bundled `warp-agent-docker` image sets this automatically. Set it yourself when running outside the bundled image.
+* **`OZ_SNAPSHOT_DECLARATIONS_SCRIPT`** - Absolute path to the script Warp invokes at the end of each cloud agent run. The bundled cloud agent image sets this automatically. Set it yourself when running outside the bundled image.
 * **`OZ_SNAPSHOT_DECLARATIONS_FILE`** - Absolute path to the JSONL file the script writes to (and Warp reads from). Warp sets this to a per-run path by default. Override it only when you want Warp to read from a static, pre-populated declarations file instead of running a script.
 
 ## Declarations file format
@@ -78,7 +78,7 @@ Malformed lines (invalid JSON, missing fields, unknown `kind`, non-absolute path
 
 ## Write a custom declarations script
 
-A custom script writes one JSON line per repository or file it wants Warp to snapshot, then exits. The bundled implementation at [`warpdotdev/warp-agent-docker/snapshot-declarations.sh`](https://github.com/warpdotdev/warp-agent-docker/blob/main/snapshot-declarations.sh) is a good reference; the minimal pattern looks like this:
+A custom script writes one JSON line per repository or file it wants Warp to snapshot, then exits. The minimal pattern looks like this:
 
 ```bash title="snapshot-declarations.sh"
 #!/bin/bash
@@ -114,6 +114,10 @@ export OZ_SNAPSHOT_DECLARATIONS_SCRIPT=/path/to/snapshot-declarations.sh
 
 For a managed [Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/) worker, set it via the worker's `environment` config so it's present when the agent process starts.
 
+:::note
+The declarations script bundled in Warp's cloud agent image is a richer version of the example above: it also honors a colon-separated `OZ_SNAPSHOT_SCAN_ROOTS` override for operators who need to scan repos outside the default workspace, uses `jq` for canonical JSON encoding instead of `sed`-based escaping, and dedupes against repo declarations already written in the same run so repeated invocations stay additive.
+:::
+
 ## Use a static declarations file
 
 If the same set of repositories or files should be snapshotted on every run (for example, an unmanaged GitHub Actions job operating on a known checkout), you can skip the script entirely and pre-populate a JSONL file:

src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx

@@ -126,7 +126,7 @@ Unmanaged agents are tracked on Warp's backend. Each run creates a persistent se
 
 Unmanaged sessions benefit from the same shared configuration as other cloud agent runs — [MCP servers](/agent-platform/cloud-agents/mcp/), [secrets](/agent-platform/cloud-agents/secrets/), Warp Drive context, and saved prompts all apply.
 
-Unmanaged runs don't ship with the bundled `warp-agent-docker` declarations script, so end-of-run workspace snapshots are a no-op by default. To enable [handoff](/agent-platform/cloud-agents/handoff/) into a follow-up run, see [Customizing workspace snapshots](/agent-platform/cloud-agents/handoff/snapshots/).
+Unmanaged runs don't ship with the bundled declarations script, so end-of-run workspace snapshots are a no-op by default. To enable [handoff](/agent-platform/cloud-agents/handoff/) into a follow-up run, see [Customizing workspace snapshots](/agent-platform/cloud-agents/handoff/snapshots/).
 
 ---