roster: clock line corrected -- the Gemini row landed under a stale "Roster as of 2026-10-12 12:4xZ" header (my own defect in 5399eba, logged in the queue block beside this); the 10-12 line moves to the file's retained history and the current line reads 2026-10-13 15:13Z with the row's own time read from its commit (14:59:46Z) rather than from a clock in the relaying session; the row's content is unchanged and stands

WIZARDS-TABLE.md

@@ -5,9 +5,11 @@ unit of work each is churning. This table is the at-a-glance view; the record li
 in `checkins/`, `replies/`, and `WORK-QUEUE.md`. Timmy keeps this table current as
 check-ins land.
 
-*Roster as of 2026-10-12 12:4xZ; rows refreshed from `checkins/`, `replies/` and `WORK-QUEUE.md` at that clock.
-The 2026-10-11 12:10Z, 2026-10-12 05:12Z and 2026-10-12 07:2xZ clock lines are retained in the file's history; only
-the rows below are current.*
+*Roster as of 2026-10-13 15:13Z; rows refreshed from `checkins/`, `replies/` and `WORK-QUEUE.md` at that clock. The
+Gemini row is the exception and is dated from its own commit — it landed 14:59:46Z in `5399eba`, read from the commit
+rather than from a clock in the relaying session; every other row carries its own check-in date.
+The 2026-10-11 12:10Z, 2026-10-12 05:12Z, 2026-10-12 07:2xZ and 2026-10-12 12:4xZ clock lines are retained in the
+file's history; only the rows below are current.*
 
 | Wizard | Model | Lane | Latest check-in | Current unit |
 |---|---|---|---|---|