docs: reconcile Day 2 release policy and output tasks

TASKS/task-41-test-stream-mode.md

@@ -24,10 +24,9 @@ inject mock chat, with alert/event triggers for subscriber, membership, and Supe
 
 ## Facts the build sits on (verified in code, 2026-09-22 research pass)
 
-- **The app is already private-only go-live** — `YouTubeStreamService.CreateBroadcast` hardcodes
-  `privacyStatus="private"` + `enableAutoStart/Stop` + `low latency`, no monitor stream
-  (`enableMonitorStream=false`), and the Go Live dialog is locked to Private. "Test" is therefore a
-  **session variant over the real pipeline**, not a new broadcast mode.
+- **Test mode is always Private** — it remains a **session variant over the real pipeline**, not a
+  new broadcast mode. The creator clarified 2026-11-04 that normal Release Go Live offers a
+  visibility choice; development/test runs stay forced Private.
 - The **liveChatId flow already exists**: `GetBroadcastLiveChatIdAsync` → `_youtubeChat.Start(liveChatId)`
   in `PrepareAndStartLiveAsync` — the "chat endpoint activation" the ask describes.
 - OAuth scope already includes `youtube` + `youtube.force-ssl` (`YouTubeAuthService.cs:18`) —
@@ -79,4 +78,4 @@ inject mock chat, with alert/event triggers for subscriber, membership, and Supe
 ## Follow-ups (NOT in this task)
 
 - Real stinger/TTS alert widgets → TASK 3 items 16/17/20.
-- Test-mode health-panel depth (per-broadcast status inside the drawer) if ever wanted.
+- Test-mode health-panel depth (per-broadcast status inside the drawer) if ever wanted.