fix: show actual debug upstream format

[orangeboyChen]

Summary

• Display the actual upstream protocol in debug request and response sections.
• Keep downstream labels based on the incoming route.
• Aggregate Anthropic content_block_delta text events so transformed responses show their content.

Validation

• bun run lint
• bun run format:check
• bun run typecheck
• bun run test:coverage (244 tests passed; 93.81% statement coverage)
• bun run build is blocked in the sandbox because Turbopack cannot bind a port.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.81%. Comparing base (7845b54) to head (2a64e50).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #110      +/-   ##
==========================================
+ Coverage   94.77%   94.81%   +0.03%     
==========================================
  Files          21       21              
  Lines        4251     4278      +27     
  Branches     1238     1249      +11     
==========================================
+ Hits         4029     4056      +27     
  Misses        222      222              

Flag	Coverage Δ
unittests	94.81% <ø> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2a64e505cc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Handle absent upstream requests without claiming Chat

When a request fails before an upstream call—such as /v1/messages with no messages—the finalized trace retains upstreamRequest: null, but this fallback labels both upstream sections as OpenAI Chat. That makes the diagnostic UI claim a protocol that was never used; return an unknown/not-sent format for null requests instead.

Useful? React with 👍 / 👎.