From 9759d84aa29336cf6a0f6ae9925f228ab9ca8916 Mon Sep 17 00:00:00 2001 From: Uruk Date: Thu, 21 May 2026 01:46:57 +0200 Subject: [PATCH] docs(casting): drop settings migration from profiles design Per review: break enableH265ForChromecast outright instead of carrying migration code. Users reconfigure; chromecastProfile defaults to auto. Co-Authored-By: Claude Opus 4.7 --- .../specs/2026-05-21-chromecast-profiles-design.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/superpowers/specs/2026-05-21-chromecast-profiles-design.md b/docs/superpowers/specs/2026-05-21-chromecast-profiles-design.md index eb751dfa6..b794ded1a 100644 --- a/docs/superpowers/specs/2026-05-21-chromecast-profiles-design.md +++ b/docs/superpowers/specs/2026-05-21-chromecast-profiles-design.md @@ -198,8 +198,10 @@ Replace `enableH265ForChromecast: boolean` with: | `chromecastProfile` | `"auto" \| "force-hevc" \| "force-h264"` | `"auto"` | | `chromecastMaxBitrate` | `number \| undefined` | `undefined` | -**Migration:** existing `enableH265ForChromecast === true` → `chromecastProfile: -"force-hevc"`; `false` or unset → `"auto"`. +**No migration.** `enableH265ForChromecast` is removed outright — no migration code. +`chromecastProfile` defaults to `"auto"`, the correct behaviour for almost every user. +Anyone who had H265 forced reconfigures it once. Avoids carrying migration logic for a +niche setting. UI: a profile-mode selector and an optional max-bitrate field in the Chromecast settings screen. `"auto"` is presented as the recommended default; the overrides are