Two small tidy-up items identified while rolling out the Spotify integration. Low-priority but straightforward; bundle together or ship separately.

A — hermes setup first-run wizard should list Spotify

Context: hermes setup (the initial guided setup a brand-new user runs) has a tool-category picker. Currently Spotify doesn't appear there — it's only reachable via hermes tools after setup completes. Same gap exists for Home Assistant and RL Training.

Why now: Low severity because most users run hermes tools eventually. Still a discoverability miss — a new user who would have enjoyed Spotify may never find out it exists unless they go looking.

Scope: Whatever pattern the first-run wizard uses for existing opt-in integrations (probably just adding an entry to the setup picker's opt-in list). If this needs new plumbing for 'opt-in integrations in first-run', that's a broader UX project — file a separate issue.

Non-goal: Don't make Spotify default-on in first-run. Stay opt-in.

B — Home Assistant interop docs note

Context: Spotify Connect already exposes HA-controlled speakers (Sonos, Echo, Nest, etc.) as Spotify devices automatically via the spotify_devices tool. The user doesn't need a Hermes-side HA↔Spotify bridge because Spotify itself handles the bridging at the device layer.

What to add: ~5-10 lines in website/docs/user-guide/features/spotify.md (new subsection under 'Using it' or within troubleshooting) explaining:

• If you have Home Assistant managing speakers that support Spotify Connect, those speakers appear in spotify_devices list automatically
• Target them by name via spotify.default_device_name (issue Spotify: add spotify.default_device_name config knob #15611) or by passing device_id explicitly
• No extra config needed — this is Spotify's native behavior, not a Hermes feature

Why it's worth documenting: Users with HA assume they need a Hermes-side integration to route Spotify to HA-managed speakers. They don't, and saying so saves them a configuration rabbit hole.

Acceptance

• A: Spotify appears in first-run setup picker; toggling it on runs the same wizard that hermes tools does
• B: Docs page has a clear 'Home Assistant-managed speakers' subsection

Both are docs/UX polish — no core code changes expected beyond the first-run picker registration for A.