Product review: a three-day meeting, end to end

[perfilev-dev]

Walked one club's meeting from the registration desk to a published results page —
practice on 7 August, qualifying on the 8th, eliminations on the 9th, four classes
covering heads-up, an index class, a time window and a bracket — and fixed what got
in the way. Every pass in the practice day and all sixteen elimination pairs ran
over the bus through the operator panel; the qualifying ETs were written into the
log by hand and are stated as invented.

Five commits, each building and testing green on its own:

• beam402 sheet names the day — --id/--name/--date/--ref, so a meeting over
  three days is three days off one rulebook instead of three hand-edited copies of
  it, which drift.
• Recording waits for the numbers — a bug, found by running a practice day: the
  staging machine goes Complete on the finish beam and the ET arrives 1.3 s later
  off the node (D25), and a press inside that beat wrote a real 11.850 down as
  -. Silently, because a pass with no time is a legitimate record — it is what a
  car that stops on the track gets.
• A day in qualifying has a board — derived by Field::qualify, the draw's own
  function, so it cannot disagree with the ladder people end up in. A practice day
  used to produce no output at all, in the CLI or the API.
• Every round is published, and everyone who is not in the field — a settled
  class used to be a final with no semi-final under it, and a facade could see that
  five entered and four qualified without being able to name the fifth.
• CLAUDE.md says race control is written — it opened by saying the repository
  has no code and nothing to build, next to thirteen crates and 325 tests.

Still open, not in this PR

• A day cannot be rehearsed. The simulator's call_up brings back the same
  pair, as it documents, so 19 cars × 3 passes give identical ETs and a club cannot
  test its own rulebook — field sizes, minimums, class windows — against the live
  loop. A scenario of several [[pass]] blocks would make one a rehearsal script.
  This is the most valuable of what is left: a rehearsal is the only way to find a
  wrong class rule before the event rather than during it.
• [event] date is one string, so a meeting running 8–9 August publishes as the 8th.
• Ties in seeding break on entry number, silently — two cars 0.0100 off their dials
  and the top seed went to the lower number.
• The entry list from the desk does not show a class's window, cut, minimum or
  scoring attempts, so somebody checking their own entry cannot see the rules they
  will be judged by.
• Pair order within a round reads 1 v 5, 4 bye, 2 bye, 3 bye — not a running order.

The facade half of this is product-review-2026-08 on Beam402/beam402-demo.

🤖 Generated with Claude Code