Spotify multi-account: second account uses first account's Soloist store/session

[Freeflyer82]

Environment

• sonn core: 4.0.0-beta.21
• Soloist: 1.3.8.36 build 1789106507 (20260911) (g5c3a2053ac)
• linux/x86_64
• Two Spotify accounts configured: AccountA and AccountB

Note: Account names and Spotify usernames in the examples below have been anonymized.

Problem

When selecting content from the second Spotify account (AccountB), the content/queue layer resolves the account correctly, but the Soloist playback process is still started using the first account's (AccountA) store/session.

Reproduction

1. Configure Spotify account AccountA.
2. Add Spotify account AccountB.
3. Select a track from AccountB.
4. Start playback.

Actual result

The content layer correctly resolves the track as belonging to AccountB:

resolvedTarget=spotify@AccountB:track:4fSWH9YqX5YGi7A5Yx5eOA

However, Soloist is started with:

store=/app/data/soloist/account-AccountA/data

and reports:

logged in as <spotify-user-A>
accountId=AccountA

The track can still play, but it is actually using AccountA's Spotify/Soloist session.

This is reproducible even after a clean core restart.

Concurrent playback

The problem becomes more visible when both accounts are used simultaneously.

While AccountB is actively playing in one zone, starting AccountA in another zone also tries to use:

/app/data/soloist/account-AccountA/data

and fails with:

Error: another session is running for data directory "/app/data/soloist/account-AccountA/data".

Expected result

Content selected from Spotify account AccountB should use a separate Soloist store/session, e.g.:

/app/data/soloist/account-AccountB/data

and authenticate as AccountB's Spotify account.

Additional observation

The account mapping appears to be correct in the content/queue layer but is lost or misapplied when the Soloist playback process is created.