Recover a conversation after the TypeScript client loses its create response

[neubig]

A conversation creation POST can succeed on the server while the TypeScript client loses its response or times out during startup. The caller then sees a failure even though the initial message may already have run; repeating the POST can repeat work.

Acceptance criteria:

• When the caller supplied a conversation ID and the POST fails without an HTTP response, reconcile through bounded GET requests for that ID.
• Never replay the creation POST or its initial message.
• Preserve explicit HTTP failures and the original transport failure if reconciliation cannot succeed; stop on authorization errors.
• Cover dropped responses and delayed creation using a real HTTP server.

Extracted from #4966 so response recovery can be reviewed independently of conversation-scoped runtime routing. Ready for development.

[github-actions]

⚠️ Not yet ready-for-dev

This issue does not yet meet the readiness criteria, so the
ready-for-dev label has not been applied (or has been removed).
The criteria are type-specific:

Bug reports (bug label, see .github/ISSUE_TEMPLATE/bug_template.yml):

• The ### Actual Behavior section must describe reproducible SDK steps
  and include a command such as python, pytest, uv, or pip.
• An ### Acceptance Criteria section with at least one checklist item (- [ ] …).

Enhancements (enhancement label, see .github/ISSUE_TEMPLATE/feature_request.yml):

• A ### Desired Behavior section.
• An ### Acceptance Criteria section with at least one checklist item.

What is missing:

• Add a ### Desired Behavior section describing the behavior you want.
• Add an ### Acceptance Criteria section with testable checklist items.

Edit the issue to address the gaps and the ready-for-dev label will be
applied automatically.

Note: Section headings require exact ### matches from the templates.
If a missing type label is reported, no action is needed from external
contributors — maintainers will add the label during triage.

This is an automated check — no AI was used to generate this comment.