Native iOS Settings sections beneath every category card for leftover exposes

[tashda]

Problem

Fans render their hero card plus a FanFeatureSections (native List Sections) underneath for any "leftover" exposes — LED, child lock, filter age, etc. The other categories don't follow this pattern:

• Lights stuff Startup + Other-advanced features behind sheet buttons (sunrise.fill, ellipsis) inside the card.
• Switches silently drop power_on_behavior, child_lock, indicator config, timers — the card only knows about state + metering.
• Climate silently drops fan_mode, preset, eco / schedule / valve / calibration features.
• Covers silently drop calibration / motor-speed style configs.

Result: a lot of meaningful configuration is either hidden in modal sheets or unreachable from the device detail screen.

Goal

Same pattern as fan, applied to every category:

1. Hero card stays exactly as it is — hero values, primary controls, category-specific affordances (Effects on lights stay as a button — they're a true light-specific control, not configuration).
2. Anything the hero doesn't bind to a primary control drops down as native iOS Settings Sections beneath the card.
3. linkquality and identify* are always hidden (they're surfaced on the device card / are noisy diagnostics).

Implementation

• New shared primitives: Shellbee/Shared/Components/SettingsFormRow.swift (Expose-driven row with inline slider for writable numerics) and Shellbee/Shared/Components/DeviceExtras.swift (eligibility filter with alwaysHidden list).
• New per-category section views: LightFeatureSections, SwitchFeatureSections, ClimateFeatureSections, CoverFeatureSections.
• LightControlCard gains a rendersAdvancedSheetsInline: Bool flag (defaults true so snapshot contexts unchanged); DeviceDetailView passes false and emits LightFeatureSections underneath.
• DeviceDetailView is reorganised around a single heroAndSettingsSections(for:state:) builder that dispatches per category.

Acceptance criteria

• Light detail no longer shows the sunrise (Startup) and ellipsis (More) buttons inside the card; those features appear as a native "Startup" / "Configuration" section beneath the card. Effects (sparkles) still in the card.
• Switch / Climate / Cover detail screens surface their previously-hidden configuration as native sections beneath the card.
• No category surfaces linkquality or identify* in any feature section.
• Hero cards (visual styling, primary controls) are unchanged.

[tashda]

Implementation summary

Shipped on PR #25.

Hero cards stay, leftovers drop to native sections

Same fan pattern, every category. Hero cards visually unchanged. Anything the hero card does not bind to a primary control drops down as native iOS Settings Sections beneath, grouped via FeatureLayout into Behaviour / Indicators / Maintenance / Status / More in canonical iOS-Settings display order — never one flat "Configuration" dump.

• Light: LightFeatureSections renders Startup + advanced. Card keeps the Effects (sparkles) button — true light-specific control. Sunrise (Startup) + ellipsis (More) buttons removed.
• Switch: SwitchFeatureSections surfaces previously-orphaned power_on_behavior / child_lock / indicator config / timers via FeatureLayout.
• Climate: ClimateFeatureSections surfaces fan_mode / preset / calibration / eco features that were silently dropped.
• Cover: CoverFeatureSections for calibration / motor speed configs.

Always-hidden list

linkquality, battery, last_seen, update, update_available, plus any identify* prefix. They're either on the device card or noisy diagnostics — never appear in any settings section, enforced by the shared DeviceExtras.eligibleLeaves(...) filter.

Startup polish (light)

Per follow-up review:

• Power-On Behavior leads. LightControlContext.startupFeatures sorts by an explicit key (power_on_behavior 0 → color_power_on_behavior 1 → state_startup 2 → current_level_startup 3 → color_temp_startup 4 → hue/saturation 5 → execute_if_off 9). The unmapped tail catches less common *_startup properties.
• Explicit display labels for power_on_behavior ("Power-On Behavior"), color_power_on_behavior ("Color Power-On Behavior"), state_startup ("Startup State") instead of the prettifier's title-cased default.
• Color Temperature parity: the Startup section's "Color Temperature" row now embeds the same LightTemperatureControl (Neutral label + tinted slider + 2.7K/3K/4K/5K/6.5K swatches) as the hero card, instead of a generic numeric slider.

Shared primitives (new)

• Shared/Components/SettingsFormRow.swift — Expose-driven row, inline slider for writable numerics (no drill-in pages).
• Shared/Components/DeviceExtras.swift — eligibility filter with always-hidden list.
• Shared/Components/DeviceFeatureSectionRow.swift — LayoutItem dispatcher (leaf → SettingsFormRow, indexed group → NavigationLink → FeatureGroupDetailView).
• Shared/Components/FeatureGroupDetailView.swift — extracted from fan, now used by every category for time1…time5-style indexed-family disclosures.

DeviceDetailView

Reorganised around a single heroAndSettingsSections(for:state:) builder that dispatches per category, replacing the prior fan-vs-everything-else if/else. Light card gains rendersAdvancedSheetsInline flag (default true for snapshot contexts like LogDetailView); DeviceDetailView passes false.

Tests

• testLightAdvancedFeaturesRenderAsSettingsSections — light advanced features render as native sections beneath the card (not behind sheet buttons inside it).
• testFeatureSectionsHideLinkqualityAndIdentify — sweeps Bedroom Hue / Bathroom Fan / Office Inovelli Fan Switch / Bedroom Curtain and asserts neither row appears.
• Existing fan checks (testFanWritableNumericRendersInline, testFanDetailOpens) untouched.

All test plan items in PR #25 confirmed by the user.