# TASK 35 — Scene-linked audio: "scenes remember the room" (queued 2026-09-01; spec approved by the creator same day)

> Catalog: [`TASKS.md`](../TASKS.md) — status and requirements live here.


**Goal:** the BRB scene mutes the mic; the Chat scene brings it back. The creator stops fiddling with
audio at transitions — the scene carries the room state. OBS needs scripts/plugins; native = the
creator-proof pitch.

**Shipped 2026-11-10.** Columns `Scene.SceneMutesMic` / `SceneMutesDesktop` (nullable = passive),
three-state checkboxes under the layers list ("When this scene goes live"), applied once at the program
transition in `TransitionToScene`. `SceneAudioTests` pins the whole rule: offline staging edits nothing,
`null` never overrides a manual mute, a scene with an opinion wins on its next entry, and all three
states survive a save/reload.

1. ✅ `Scene` gains nullable `SceneMutesMic` / `SceneMutesDesktop` — `null` = don't touch (the default;
   scenes are passive until told). Schema column bump + roundtrip.
2. ✅ Applied on **live transitions only** (thumbnail click / hotkey), ONCE at entry — never on
   offline staging (no surprise stream-state edits while auditioning).
3. ✅ The creator is boss: a manual mute/unmute mid-scene is never overridden until the next entry.
4. ✅ BRB ships `SceneMutesMic = true`; other scenes default `null` — creator's choice.
5. ✅ Edit UI: two checkboxes in the scene's Properties section (left panel, edit mode) — no new chrome.
6. ✅ Test (the ONE): transition applies scene state; `null` leaves state untouched; manual override
   survives until the next entry.