fix(connect): hydrate status metadata + improve device UX

[mbelinky]

Summary

This improves reliability of spogo status (especially with the connect engine) when Spotify connect-state payloads omit track/device metadata, and upgrades device management ergonomics.

Problem

Some devices/sessions return sparse connect-state payloads where the currently playing item has a URI/ID but no name/album, and the active device has little to no metadata. This made status outputs inconsistent (track/device fields often empty) and could lead to slow/hanging status calls when fallback paths were slow.

Fix

• Connect playback/status now performs best-effort metadata hydration via Web API:
  • Use Web API /me/player to fill missing track/device fields when available.
  • If the track still lacks a name, hydrate via Web API GetTrack first (fast), then fall back to the existing connect GraphQL trackInfo.
  • If device metadata is missing, hydrate via /me/player/devices by ID, and as a last resort pick the single active Web API device.
• Hydration calls are bounded with short per-call timeouts so status --json stays responsive under automation.
• Improve connect-state parsing for more playback/device shapes (metadata keys, track_window, etc).

Device UX

• Add spogo device show and spogo device clear.
• Add spogo device set --save to persist selection to the current profile.
• Add a shared resolver for device selection with exact and unique partial matches (name/id).
• connect engine honors --device/profile device by auto-transferring before playback commands.

Tests

• Added unit tests covering connect status hydration paths (track/device), device selection resolver, and CLI device commands.
• Updated test HTTP helpers to include ContentLength so Web API JSON decoding behavior matches production client logic.

Docs

• Document new device subcommands and note connect status hydration behavior in README/spec/changelog.

[steipete]

Rebased review against current main: not merge-now safe.

Current blocker: this still does not fix issue #8. still routes through Connect transfer, and the failure path remains in when neither origin nor active device is present.

Current architecture also diverged since this PR was opened: the old monoliths were split, and parts of this PR now overlap landed work in #7 and #15. This needs a manual split/port, not a straight rebase.

Recommended split:

• status/device hydration improvements
• selector UX improvements
• separate transfer fallback fix for Unable to set device #8

Keeping this open for a narrower follow-up, but not merging as-is.

[steipete]

Follow-up with the exact blocker text.

This still does not fix issue #8. device set still routes through Connect transfer, and the failure path remains missing origin device id in internal/spotify/connect_commands.go when neither origin nor active device is present.

Current architecture also diverged since this PR was opened: the old monoliths were split, and parts of this PR now overlap landed work in #7 and #15. This needs a manual split/port, not a straight rebase.

Recommended split:

• status/device hydration improvements
• selector UX improvements
• separate transfer fallback fix for Unable to set device #8

Keeping this open for a narrower follow-up, but not merging as-is.

[steipete]

Root issue is fixed on in c613e96.\n\nThat change handles the missing-origin-device path directly by falling back to Web API transfer when Connect state has no source device.\n\nThis PR still looks like separate status-hydration / device-UX work, and it still needs a rebase/split before merge.

[steipete]

Root issue #8 is fixed on main in c613e96.

That change handles the missing-origin-device path directly by falling back to Web API transfer when Connect state has no source device.

This PR still looks like separate status-hydration / device-UX work, and it still needs a rebase/split before merge.

[steipete]

Triage note: not merging this as-is today. It is dirty against current main and mixes several concerns: status hydration, Connect state parsing, device commands, saved-device config, and selector matching.

Some adjacent fixes are already on main now (#16, #21, #24, plus the existing artist/status extraction work). The useful remaining pieces here should be split/rebased into smaller PRs, especially if we still want device show, device clear, or persisted device selection.

[steipete]

Closing this stale broad PR after current-main triage.

The original missing-origin device path was fixed on \ in c613e96, and more adjacent Connect/status fixes have landed since then (#16, #21, #24, plus the current sparse metadata fixes released in v0.3.0). This branch is now conflicting/dirty and mixes several separable changes: status hydration, Connect-state parsing, device commands, saved-device config, and selector matching.

There are still useful ideas here, but they should come back as smaller rebased PRs. Good follow-up slices would be:

• \ / \ / \
• selector matching as a focused helper + tests
• bounded status hydration only if current \ still misses a concrete payload shape

Thanks for the work here; closing to keep the queue actionable rather than trying to revive this branch wholesale.

[steipete]

Correction to the close note above, where Markdown backticks were eaten by my shell.

Closing this stale broad PR after current-main triage.

The original missing-origin device path was fixed on main in c613e96, and more adjacent Connect/status fixes have landed since then (#16, #21, #24, plus the current sparse metadata fixes released in v0.3.0). This branch is now conflicting/dirty and mixes several separable changes: status hydration, Connect-state parsing, device commands, saved-device config, and selector matching.

There are still useful ideas here, but they should come back as smaller rebased PRs. Good follow-up slices would be:

• device show / device clear / device set --save
• selector matching as a focused helper + tests
• bounded status hydration only if current main still misses a concrete payload shape

Thanks for the work here; closing to keep the queue actionable rather than trying to revive this branch wholesale.