Cloud session uses stale .seed.bundle — repo not refreshed between sessions

Description

Cloud sessions (claude.ai/code) clone from a cached .seed.bundle instead of a fresh GitHub clone. The bundle is not refreshed between sessions, resulting in stale code even in brand-new sessions.

Evidence

• git reflog in cloud session shows: clone: from /home/user/.seed.bundle
• .git/config has no [remote "origin"] section (intentionally removed)
• Two separate sessions created days apart had the same stale HEAD

Reproduction

1. Push commits to a private GitHub repo from local CLI
2. Wait any amount of time
3. Start a new cloud session (e.g., via ultraplan or claude.ai/code)
4. Run git log --oneline -1 — HEAD is days behind the latest push
5. git remote -v returns empty (no remote configured)
6. git fetch fails with "could not read Username" (no credentials)

Observed behavior

| Environment | HEAD | Date |
|-------------|------|------|
| Local (WSL) + GitHub origin | a056b22 | Apr 11, 2026 02:19 KST |
| Cloud session (new) | bc522d8 | Apr 8, 2026 23:46 KST |

Gap: 6 commits, 3 days stale. Multiple new sessions all cloned from the same outdated bundle.

Expected behavior

Each new cloud session should reflect the latest state of origin/main at session creation time, as stated in the docs: "a fresh clone of your repository."

Environment

• Repo: private GitHub repo
• Local: WSL2 + Claude Code CLI
• Cloud: claude.ai/code (ultraplan sessions)