[mogita]

Problem

The Stream API key is an identifier, yet CI reads it from a repository secret. A secret cannot be read back, so nobody can see which test app CI runs against.

Solution

The workflows read the key from the STREAM_CHAT_API_KEY Actions variable. The API secret stays a repository secret.

How to verify

1. The CI run on this PR passes with the key coming from the variable.
2. After merge, the scheduled test workflow passes on the default branch and the STREAM_CHAT_API_KEY repository secret is deleted.

---

Note

Low Risk
Workflow-only change; tests behave the same if the variable holds the former secret value, with a small operational risk if the variable is not configured before removing the old secret.

Overview
CI and scheduled test workflows now inject STREAM_KEY from the GitHub Actions variable STREAM_CHAT_API_KEY instead of a repository secret, so the test Stream app key is visible in repo settings while STREAM_SECRET still comes from secrets.STREAM_CHAT_API_SECRET.

No application or test code changes—only the two workflow env blocks in ci.yml and scheduled_test.yml.

^{Reviewed by Cursor Bugbot for commit 6e4fdea. Bugbot is set up for automated code reviews on this repo. Configure here.}