Board.Position is one order for the whole deployment, and once every
member makes their own boards that is nobody's to set. The home page and
the switcher now follow an order that belongs to the reader: pinned
first (oldest pin leading, so the group never shuffles), then the boards
they opened most recently, then Position for everything they have never
touched — which is why nothing reshuffles on deploy day and why Position
stays until nothing reads it.

BoardOrder is a table of its own rather than two columns on BoardMember,
because an Everyone board has no grant row for most of the people who
see it: putting the order there would mean minting a grant the first
time somebody pinned an open board. Nothing on it is encrypted — ORDER
BY is the entire point of the table.

Recording "opened" is a write per board visit, which LastPage refused
for the last page. The trade differs: that is a write per *page* about
this *browser*, which a cookie says perfectly well, while this is one
row per board opened and has to be the same order on a phone as on a
laptop. MarkOpenedAsync is the one mutating method in the app that fires
no BoardNotifier event, and argues why in place; pinning does fire one.

The "for you" strip above the tiles — the cards you are on and the cards
due this week, across every board you can see — was measured before it
was built, as the issue asked. It is two passes: one narrows in SQL (a
CardAssignee's DID is plaintext, and a due date's *nullness* never
reaches the converter) and decrypts only the date, and one reads the
titles of the six that survive. At 6,000 cards over 24 boards that is
~1.3 MiB against ~4.8 MiB for the obvious single projection, and about a
third of one board load. The numbers are in docs/data.md.

ForYouTests pins the ranking rule; one e2e test in home.spec.js pins the
pin, the switcher following it, the opening being remembered, and a
strip row opening the card it names.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

@@ -94,3 +94,2 @@
             "The board on a phone gives its width to the cards: less space around them, so titles fit on one line and more of the column is on screen — and the column's name starts where its cards do.",
-            "Boards now have admins of their own, given on the board's access page — several are possible, handing a board over is one tick, and two boards may share a name.",
-            "The members page is now for the deployment's configured admins. An admin promoted here who is not in that configuration no longer sees it — who runs a board is decided on that board's access page.",
+            "Boards now have admins of their own, given on the board's access page — several are possible, handing a board over is one tick, and two boards may share a name. The members page is the deployment's own admins alone now.",