resumed cloud runs have no prior context; they start on fresh `master` pulls

[adboio]

scenario:

1. start a cloud run
2. it generates a PR
3. go back to it later with a followup
4. cloud session resumes

the new cloud session seems to have no context on the existing branch or PR

concrete example:

• a cloud session generated this PR: fix(product-tours): use dedicated color instead of borrowing surveys color posthog#53329
• i went back to as for a change
• i see these logs:

[info] Fetching task details
[info] Resuming environment from snapshot for posthog/posthog
[info] Checking out branch master
[info] Starting agent server
[info] Agent server started at https://a-ta-01knmhkzhpf83zz6fx697ghan5-c2prsbj3jfyktofl3wq9pozt9.w.modal.host
[info] Session initialized successfully
[info] Agent version: 2.3.131
[info] Sending resume message {"taskId":"cf2151f6-506c-4dc4-837a-994d6c3790b3","conversationTurns":2,"promptLength":4441,"hasPendingUserMessage":true,"snapshotApplied":true}

• the initial prompt:

You are resuming a previous conversation. The workspace environment (all files, packages, and code changes) has been fully restored from where you left off.

Here is the conversation history from the previous session:

**User**: change the default product tours color options to be more posthoggy

**Assistant**: The manifest is using survey colors. Let me check what product-specific color options are available.No `--color-product-tours` CSS variable exists yet, and the manifest is borrowing the surveys color (`rgb(243 84 84)` - red). I need to add a dedicated product tours color and update the manifest.

Let me check what other manifests look like for color patterns and pick something "PostHoggy" — a unique color not already taken.

Looking at the existing palette, a warm teal/cyan-ish tone around `rgb(0 171 145)` would be distinctive and PostHog-esque. Let me add the CSS variable and update the manifest.Now let me add the product tours color and update the manifest. I'll pick a vibrant coral-orange tone (`rgb(255 106 61)`) — it's warm, energetic, and distinctly PostHoggy while not duplicating existing colors.Now let me also check if product tours colors are referenced anywhere else.The jsonl file is a mock/snapshot — not relevant. Let me verify the final state of the manifest.Good. Now let me create the branch, commit, and PR.Done. Here's what changed:

**CSS** (`frontend/src/styles/base.scss`): Added two new variables:
- `--color-product-product-tours-light: rgb(255 106 61)` — vibrant coral-orange
- `--color-product-product-tours-dark: rgb(255 130 92)` — lighter variant for dark mode

**Manifest** (`products/product_tours/manifest.tsx`): Updated all three `iconColor` references from `var(--color-product-surveys-light)` to `var(--color-product-product-tours-light)`.

PR: https://github.com/PostHog/posthog/pull/53329

The user has sent a new message:

[the message i sent]

• the agent ran git add products/product_tours/manifest.tsx && git commit -m "$(cat <<'EOF' fix(product-tours): wire dark mode color var…

[detached HEAD 98dbfa3536] fix(product-tours): wire dark mode color variant into iconColor arrays
 1 file changed, 12 insertions(+), 3 deletions(-)

• the agent tried to push, failed git push origin HEAD:product-tours-color-update

Exit code 1
error: The destination you provided is not a full refname (i.e.,
starting with "refs/"). We tried to guess what you meant by:

- Looking for a ref that matches 'product-tours-color-update' on the remote side.
- Checking if the <src> being pushed ('HEAD')
  is a ref in "refs/{heads,tags}/". If so we add a corresponding
  refs/{heads,tags}/ prefix on the remote side.

Neither worked, so we gave up. You must fully qualify the ref.
hint: The <src> part of the refspec is a commit object.
hint: Did you mean to create a new branch by pushing to
hint: 'HEAD:refs/heads/product-tours-color-update'?
error: failed to push some refs to 'https://github.com/posthog/posthog.git'

• the agent tried again, worked git push origin HEAD:refs/heads/product-tours-color-update

remote: This repository moved. Please use the new location:        
remote:   https://github.com/PostHog/posthog.git        
remote: 
remote: Create a pull request for 'product-tours-color-update' on GitHub by visiting:        
remote:      https://github.com/PostHog/posthog/pull/new/product-tours-color-update        
remote: 
To https://github.com/posthog/posthog.git
 * [new branch]            HEAD -> product-tours-color-update

• i tried asking it what branch it started on, and i got this

The previous session's commits are gone — the workspace was restored to a fresh state on master (8ce5d3e39a). The branch I created and the commits from the previous session weren't preserved.

I started from master. The original PR branch and commits need to be recreated. Want me to redo the changes (both the initial color change and the dark mode fix) and force-push to the existing PR branch?