feat: sort the first-run game picker alphabetically

The picker took `available` in feed order — whichever game happened to hold the first event row — which means something everywhere else in the app and nothing on this screen, where the reader is scanning for the two or three names they already know. Sorted on the name printed on the button rather than the LaneId, since the id is not what a reader sees, and through localeCompare rather than `<`, because a code-point sort files hololive Dreams after every capitalised game instead of between Genshin and Honkai. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
2026-08-20 05:34:00 +02:00
parent 24832844a6
commit 7b6ee62235
3 changed files with 71 additions and 5 deletions
@@ -279,7 +279,10 @@ Before any events are shown, the reader picks which games they play, and how the
 them. A calendar full of games they
 don't play is worse than an empty one — it buries the thing they came for. Nothing is preselected
 and the button stays disabled until something is chosen; guessing on their behalf and hoping they
-notice is worse than asking. The choice is stored as *hidden* games, the inverse — which is a storage
+notice is worse than asking. **The games are listed alphabetically by name**, not in feed order:
+everywhere else a lane's position carries meaning, but here the reader is scanning for the two or
+three names they already know, and a list ordered by which game happened to hold the first event row
+gives them nothing to scan by. The choice is stored as *hidden* games, the inverse — which is a storage
 shape, not a policy: what happens to a game added later is decided separately, below.

 **A game added later arrives switched off.** Adding a source is our decision, not the reader's, and