docs(handoff): address two missed Rachael comments on cloud-to-cloud

I missed two of @rachaelrenk's review comments on the cloud-to-cloud
page in earlier passes because they weren't returned by the first
`gh pr view` query. Applying them now.

cloud-to-cloud.mdx
- "ambient agent run" -> "background cloud agent run". Rachael flagged
  "ambient agent run" as abstract/internal-feeling; "background cloud
  agent run" keeps the example concrete and matches the user-facing
  framing on the surrounding pages. Per her suggested edit verbatim.
- Removed `blocked` from the example list of terminal states. The API
  treats BLOCKED as terminal for cancellation purposes, but the spec
  describes it as "awaiting user input or approval" — so it isn't a
  natural place to send a follow-up via cloud-to-cloud handoff
  (responding to the prompt on the original run is the right path).
  Added a sentence to the prereq calling that out explicitly so
  readers don't try to hand off a blocked run.

Validation
- python3 .agents/skills/style_lint/style_lint.py --changed -> 0 issues.
- python3 .agents/skills/check_for_broken_links/check_links.py
  --internal-only -> 0 broken (2,439 internal links, 321 files).

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

Author: hongyi-chen

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

@@ -12,7 +12,7 @@ Hand off a cloud agent run to a fresh cloud session when the original session ha
 Use this handoff direction when:
 
 * You want to send a follow-up to a cloud agent after its session has ended.
-* You want to continue an ambient agent run — an agent that runs in the background, such as a scheduled or integration-triggered run — while preserving it as a single unit of work in the [management view](/agent-platform/cloud-agents/managing-cloud-agents/).
+* You want to continue a background cloud agent run, such as a scheduled or integration-triggered run, while preserving it as a single unit of work in the [management view](/agent-platform/cloud-agents/managing-cloud-agents/).
 
 ## What carries over
 
@@ -26,7 +26,7 @@ If applying any change fails, the agent reports what couldn't be applied and pro
 
 ## Prerequisites
 
-* **An ended cloud agent run** - The run must be in a terminal state — for example, succeeded, failed, blocked, or canceled — and have an associated agent conversation. Very old runs that predate the agent conversation model can't be continued via handoff.
+* **An ended cloud agent run** - The run must be in a terminal state — for example, succeeded, failed, or canceled — and have an associated agent conversation. Blocked runs that are waiting on user input or approval aren't continued through cloud-to-cloud handoff; respond to the prompt on the original run instead. Very old runs that predate the agent conversation model can't be continued via handoff.
 * **A snapshot from the prior session** - Cloud agent runs capture a workspace snapshot at the end of each session. If the prior session couldn't capture one (for example, due to a transient storage error), the run still continues — it just starts without restored workspace state.
 * **Access to the run** - You need permission to submit follow-ups for the run. For team runs, this is typically any team member. Cloud runs that originated from a local-to-cloud handoff can be continued only by the user who created them, not by other team members.