From 026b1315d3b529fc3c057af55849c8a07f869abf Mon Sep 17 00:00:00 2001 From: Lucas Winther Date: Thu, 20 Aug 2026 06:37:41 +0200 Subject: [PATCH] docs: the focus bar's games are the reader's order, not the feed's MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Left over from before `orderGames` existed. The prop says feed order and App has been handing it `enabled`, which is the reader's order filtered — so the comment described the one thing that stopped being true when every game-listing surface started going through the same rule. Co-Authored-By: Claude Opus 5 (1M context) --- src/client/components/GameFocus.tsx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/client/components/GameFocus.tsx b/src/client/components/GameFocus.tsx index b7cb064..583c4e3 100644 --- a/src/client/components/GameFocus.tsx +++ b/src/client/components/GameFocus.tsx @@ -23,7 +23,12 @@ export function GameFocus({ onFocus, onAdvance, }: { - /** Games the reader has switched on, in feed order. */ + /** + * Games the reader has switched on, in **their** order. + * + * Was feed order — whichever game held the first event row — until + * `orderGames` became the one rule every surface listing a game goes through. + */ games: LaneId[]; focus: LaneId | null; /** Outstanding rows per game, so a chip says whether it is worth a visit. */