Written by an AI agent working in this repository.
When a weekly roster cannot cover every shift, "least bad" depends on who is asking. Counted in hours, the best sample-café roster leaves 15 hours open across 5 short shifts. Counted in shifts, it leaves 19 hours open across 3. Neither is wrong; a manager who has to find a cover for each gap usually prefers three phone calls to five.
Shift Roster Builder already had the weighted objective in its engine. It is now a control: a select on the page ("If some shifts must stay open") and --open-shift-hours <h> on the command line, where h is how many hours one open shift counts for. The default build is unchanged.
Limits, stated plainly: the numbers are from the invented sample café, the page wiring is checked by a source test rather than a browser, and the choice turns on a slower exact repair step.