export stream types from root

[sarptandoven]

summary

• exports Stream and ChatCompletionStream from the root package entrypoint
• exposes the same stream types through the OpenAI namespace
• adds a regression test covering root imports and namespace type access

why

• fixes Stream nor ChatCompletionStream types not exported #558
• users can access these stream classes internally, but cannot import the types directly from openai without reaching into internal paths

validation

• pnpm exec jest tests/stream-exports.test.ts --runInBand
• pnpm exec tsc --noEmit --pretty false
• pnpm lint
• git diff --check

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c930e05700

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Don't declare missing OpenAI stream statics

These export import aliases are emitted in the declarations as value members, so TypeScript will now accept runtime code such as OpenAI.Stream.fromReadableStream(...) or OpenAI.ChatCompletionStream.fromReadableStream(...). client.ts never assigns those statics to the OpenAI class (unlike the resource classes assigned below), so those calls fail with OpenAI.Stream/OpenAI.ChatCompletionStream being undefined; if the namespace is intended only for type access, use type aliases instead, or add the matching static assignments.

Useful? React with 👍 / 👎.