Hidden setting does not clear the stored value

A stored preference can name an effect this device cannot draw. Hiding an option from a settings picker only stops a user from choosing it from now on — it does nothing about a value already sitting in the preference store, so the real defence has to live at the render site instead, and it takes the shape of a capability boolean: a small function each render site calls itself, right next to the preference read, instead of trusting that Settings already filtered the value. Building and calling that boolean correctly is most of what this skill is about — get it wrong and the render-site defence collapses back into "the picker already handled it."

Some Compose modifiers do not fail when the platform cannot honour them — they render as a no-op, with no exception and nothing in the log. Modifier.blur on Android is one: below API 31 there is no RenderEffect to back it, so the modifier simply draws the content unblurred. A style built around that blur being present therefore needs a real capability check, not a version comment:

// adapted — three files combined; each file's own doc comment is replaced with a one-line label
expect fun isLyricsBlurSupported(): Boolean