debug-claude-session

# Debugging a Claude Code session Given a Claude Code **session ID**, pull the local transcript (what the client saw) and the corresponding production cloud logs (which model/provider served it), then correlate them to understand the wire-format translation. The local `.jsonl` is ground truth for *what rendered*; the cloud logs confirm *what the upstream sent*; the `internal/translate` code explains *why the wire shape looks that way*. ## Setup: Cloud deployment config Before starting, create a gitignored config file with your deployment's cloud logging details: ```bash cat > .claude/skills/debug-claude-session/.deployment.json <<'EOF' { "cloud_provider": "gcp", "project_id": "your-project-id", "region": "us-central1", "service_name": "router", "log_command_template": "gcloud logging read ... --project {project_id} --format=json" } EOF git add .claude/skills/debug-claude-session/.deployment.json.example # .deployment.json itself should be gitignored ``` If `.deployment.json` is missing, the agent will prompt you for these details and walk you through creating it. The file is gitignored and contains no secrets — it's just the service/project/region names needed to construct cloud log queries. ## Critical gotchas (read first) - **The transcript is the source of truth for rendering.** What the client showed is exactly the assistant `message.content` blocks in the `.jsonl` — not what you assume the model emitted. Always inspect block contents (decode fields, chec...