austinried 72330387c8 fix resuming after removing the playing track in a shuffled queue ...

The "play whatever now fills the removed track's slot" branch was written
for the old re-derive model: it mapped the removed canonical slot through
the new permutation, which now (with the fixed shuffle order) picks an
unrelated track. Removing the playing track should just resume at the same
slot, which holds whatever was next.

- Drop the special slot branch: `position == current` resumes at `current`
  for shuffled and unshuffled alike. Without a block that is the next
  shuffled track; with one, re-anchor the block from the removed track onto
  the track now preceding that slot so the block takes the slot and plays
  next (previously it was stranded behind a random track).
- Tests assert the immediate playing track, not just what is upcoming, which
  is why they missed this. Both new tests fail on the previous commit.
- Cover advancing out of a block track and moving a block track while
  shuffled (the last items from the QA review).

2026-10-04 00:30:01 +00:00

..

schemas/com.subtracks.data.db.SubtracksDatabase

rework: derive the shuffle order from a seed on top of the up-next queue

2026-10-04 00:30:01 +00:00

src

fix resuming after removing the playing track in a shuffled queue

2026-10-04 00:30:01 +00:00

build.gradle.kts

parse Subsonic dates with java.time via core library desugaring

2026-10-04 00:29:55 +00:00