v0.8.0 — the board replays what everyone else did, instead of arriving rearranged

TODO #13, #15 and #18 — Gitea#20 steps 2-4 pointed at a seated player's own screen.
Every accepted intent, and every automatic phase that does anything, becomes an
ordered presentation step. A bot's whole switching turn used to land in one push;
now it arrives as a run of steps, the district panel follows whoever is acting,
and a [N behind] … [Skip] row says how far the board is from the game.

Solitaire runs the same path — one collector inside submit(), which both session
kinds already funnel through — which is where its automatic phases finally get a
visible beat.

Dwell is assigned by kind: switching holds the screen, turn bookkeeping costs
nothing, and the clock turning over earns the beat. Tunable per viewer without a
rebuild, and off entirely at pace 0.

Also: switching was the one class of action logging unattributed, and now names
its train. Reasoning, measurements and the three things that turned out wrong are
in CHANGELOG.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X6cF1iYvJ1kNmzYBzu4QX6
This commit is contained in:
Jesse.Markowitz
2026-09-09 15:31:46 -04:00
co-authored by Claude Opus 5
parent 312e0301e0
commit 02289e94b8
25 changed files with 2669 additions and 145 deletions
+12 -1
View File
@@ -35,8 +35,19 @@ deliberately no longer names one: it went stale for six releases.
reload; anybody may leave and the host may clear a chair; and the four transient signals that make
a game feel alive — sound, the timetable flash, an announcement, the badge on the card you just
drew — reach a remote client, which they did not before v0.7.0. What is still open is in `TODO.md`
under Multiplayer — chiefly that **a player cannot see what the others did**, and that a lost
under Multiplayer — chiefly that a lost
session token still locks someone out of a running game from a genuinely fresh browser.
- **Watching the table — v0.8.0.** Every accepted move, and every automatic phase that does
anything, becomes an ordered **presentation step**: the board replays other people's turns instead
of arriving already rearranged. This is what closes "a player cannot see what the others did",
which stood open through v0.7.x. A bot's whole switching turn used to land in one push, because
`driveBots()` plays it out before the push goes back; now it arrives as a run of steps, the
district panel follows whoever is acting, and a `[N behind] … [Skip]` row says how far the board is
from the game. Dwell is assigned **by kind** — a switching move holds the screen, turn bookkeeping
costs nothing — and is tunable per viewer without a rebuild. Solitaire runs the same path, which is
where its automatic phases finally get a visible beat.
**Not yet checked in a browser:** the mechanism is proven server-side against a live SSE stream and
the page is proven not to throw, but nobody has watched a bot switch on screen.
- **Not built** — the opponent-directed cards (the Action and Space-use categories, held out of every
deck until they have an implementation, along with the defensive cards whose only purpose is to
answer them), and real audio. No screen offers a control for the opponent cards any more: the