feat: ship chats.streamChat() with SSE support

[rodnnnney]

Summary

streamChat was documented on docs.textql.com but missing from the generated SDK. Root cause: the registry spec labels the stream response application/x-ndjson, and Speakeasy gates JSONL/NDJSON stream generation (jsonlResponses) behind its enterprise tier — so codegen silently skipped the operation. SSE generation works on the current tier.

The endpoint is served by demo2's platform v2 SSE handler (TextQLLabs/demo2#13014), which streams {result: Cell} / {error: Status} envelopes as data: frames.

Changes

• Overlay (.speakeasy/speakeasy-modifications-overlay.yaml): normalizes the stream operation to the SSE envelope contract — 200 is text/event-stream with typed data.result: Cell / data.error: Status, errors are application/json. Written to be robust against any registry snapshot state; becomes a harmless no-op once demo2 publishes the SSE spec at the source.
• Regenerated SDK: ships textql.chats.streamChat() returning EventStream<StreamChatEvent>. Version 1.1.1.

Usage

const result = await textql.chats.streamChat({ chatId, body: { latestCompleteCellId } });
if (result instanceof EventStream) {
  for await (const event of result) {
    if (event.data.result) { /* next cell */ }
    if (event.data.error)  { /* stream ended with an error */ }
  }
}

Cross-repo context & merge order

• TextQLLabs/demo2#13014 — adds the endpoint (native SSE handler) and publishes the contract in the OpenAPI source.
• feat: ship chats.stream_chat() with SSE support textql-python-v3#12 — same fix for the Python SDK.

This PR can merge independently, but the generated method only works once demo2#13014 deploys (the endpoint doesn't exist in production until then). On merge, the Publish workflow releases to npm and auto-opens the docs-sync PR in demo2.

Follow-ups

• Drop the overlay normalization actions once a prod deploy republishes the spec (they'll be no-ops).
• examples/chat-demo still uses a raw-fetch NDJSON parser; switch it to chats.streamChat() once this is on npm.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​sveltejs/​kit@​2.70.1
	@​sveltejs/​adapter-auto@​7.0.1
	@​sveltejs/​vite-plugin-svelte@​7.2.0
	vite@​8.1.5
	svelte-sonner@​1.1.1
	tailwindcss@​4.3.3
	svelte@​5.56.7
	@​tailwindcss/​vite@​4.3.3
	typescript@​6.0.3
	svelte-check@​4.7.3

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: examples/chat-demo/package-lock.json → npm/vite@8.1.5 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report