What changed

The device settings screen now adapts to your AirPods' current state instead of showing every section at once.

• Out of range: only device info + a "bring AirPods nearby" hint.
• Nearby but not connected: only device info + the existing connect prompt.
• Profile has no paired Bluetooth device: a banner appears with a one-tap shortcut to fix the profile (same banner the dashboard already uses).
• The "advanced settings unavailable" card (shown on phones whose Bluetooth stack can't do AAP) was moved to the bottom — it no longer dominates the page on incompatible phones.
• The "changes apply when AirPods are in ear" hint is now a snackbar that fires after you change a setting, instead of a passive banner above all settings.

Technical Context

• Reactions are now gated on state.isClassicallyConnected. They assume this phone is the audio target (auto-pause / sleep-pause / CA), so showing them in BLE-visible-only state was misleading — NotConnectedCard already covers that prompt.
• Missing-paired-device case reuses MissingPairedDeviceBanner from the overview cards. New navToEditProfile() on the viewmodel routes to Nav.Main.DeviceProfileCreation. Every other state card is gated on device.hasSelectedPairedDevice to avoid double-messaging.
• Pending snackbar fires on the false→true transition of hasPendingSettings, with null initial state to avoid firing on screen entry when something was already pending. No new strings — device_settings_pending_info is reused.

Review checklist

• Out of range → DeviceInfo + "Device not nearby" infobox only.
• BLE-visible / not classically connected → DeviceInfo + NotConnected only (no Reactions).
• Classic only (no AAP) → DeviceInfo + Reactions + AapUnavailable at bottom.
• Fully connected → all setting cards.
• Profile with no paired Bluetooth device → DeviceInfo + missing-paired banner; tap → profile editor.
• Change a setting while AirPods are in case → snackbar fires once.