Set up the room
Three numbers define the room. The user needs to know immediately whether those numbers work for the number of guests they have.
This is the landing screen and the first thing anyone sees.
Acceptance criteria
- Event name, round tables, seats each, top table seats. All editable
- Total seats calculated as
roundTables × seatsEach + topTableSeats - Capacity readout recalculates live, with three states: enough with slack, exactly enough, short
- Short is a warning. It never blocks anything and it is not styled as an error
- Status strip shows guests loaded, seats configured, and whether a plan exists
- First visit shows the form with no capacity readout, because there are no guests to compare against
Comments
Build feedback for TT-3.
1. The short-state suggestion verb. TT-3's criteria don't mention the suggestion line at all, and KB-6 publishes exactly one worked example of it — the slack case, "Drop to 8 tables: 70 seats for 70 guests. Exactly enough." We were asked to build the line, which meant specifying the case KB-6 doesn't draw. We've used "Go up to 8 tables: …" as the counterpart verb, on the reasoning that it preserves the published shape (verb plus target count) rather than switching to a delta like "Add 2 tables". The line only ever proposes a room that seats the guest list exactly; where no whole number of tables lands on exact, there's no line. It's static text, not a control — KB-6 brackets every field and button on that screen and doesn't bracket this one.
2. Digits, not words. KB-6's readout prose reads "Eight spare"; we render "8 spare". KB-6 contradicts itself here — the scenario cards on the same page read "8 spare", "16 spare", "none spare" — and the spelled form has no tabular figure variant, which fights KB-6's own "every figure in it is tabular, or it jitters as you type". At Celebrity scale it would read "Sixteen spare", and a short room would read "One hundred and thirty-two short". We've gone with digits deliberately. Happy to reverse it if the prose was the intent.
The short-state readout sentence ("40 seats for 70 guests. 30 short.") is likewise ours — KB-6 publishes no short example — built to match the shape of the two it does publish.