Upstream API endpoint change from sharp-api

[github-actions]

Upstream API Endpoint Change

Source repo: sharp-api
Commit: fcccb3204333f91d01e5eac24a62560d44225ae0
Changed files: src/app/api/v1/stream/route.ts

Review Checklist

• Check if API reference docs need updating for changed endpoints
• Verify request/response examples still match actual API behavior
• Update any new query parameters or headers
• Add documentation for any new endpoints
• Update SDK examples if affected
• Test code examples against live API

Context

This issue was auto-created by a repository_dispatch event from sharp-api.
API route handlers were modified, which may require documentation updates.

If no action is needed, close this issue with a comment explaining why.

[Mlaz-code]

Legacy dispatcher (Mlaz-code/sharp-api TS) is retired and was replaced by Mlaz-code/sharp-api-go (Go rewrite). The new notifier (sharp-api-go workflow notify-docs.yml) dispatches upstream-api-endpoint-change only after a successful production deploy, and the receiver dedups all dispatches in a UTC day into a single rolling "Docs review: upstream API changes (YYYY-MM-DD)" issue. Bulk-closing 185 unread legacy tickets (Feb 18 → Mar 19, 2026) — none were ever triaged. See https://github.com/Mlaz-code/docs.sharpapi.io/pull/N for the dedup PR.