d7d9209795
Rewrite of the original component-local `editingNonDefault` computation onto the existing scope architecture (owner's ask: "use the same existing architecture" as the Capabilities/toolset scope handling). - store/settings-scope.ts gains `$settingsScopeEditsNonDefault`, a computed over `$settingsScopeProfile` × `$profiles`, so "the settings pages are editing a non-default profile" is a store fact any surface can subscribe to, not a per-component recomputation. - profile-scope.tsx reads `$settingsScopeProfile` for the selected chip (instead of re-deriving `override ?? active`) and the new selector for the loud/quiet note. User-visible outcome is unchanged: accented note for any non-default target, override or not; quiet note for an explicit override onto the default; nothing when following the active default. - Review: an unloaded roster (no `is_default` entry yet) used to suppress the note exactly at the landing moment where a bot may already be the active profile. The selector now assumes the root profile's canonical key as the default, so an unknown default fails loud, not quiet. The four-cell truth table is documented at the JSX conditional. - settings-scope.test.ts pins the selector across active-profile, override and unloaded-roster inputs; the component tests from the original PR are kept as-is and still pass.