Bakery scheduling supervisor - the weekly schedule draft tool: skill tags and availability in, a tweakable draft with conflicts flagged red out (have a coding agent build it)

Build me a single-file HTML weekly scheduling tool for a bakery
shop. Double-click to open in a browser, no network, no
dependencies installed, data stays on the local machine. Build it
as a scheduling supervisor's drafting board, not an
auto-scheduler.

Data entry:
1. Staff roster: name, skill tags (multi-select: oven opening /
   cake decorating / cashier / stocking), certification level
   (independent operator / assist), weekly hour cap per person
2. Availability: which blocks each person cannot work this week
   (day plus block checkboxes), supporting both whole-day and
   partial-block unavailability
3. Block requirements: total headcount needed per trading block,
   plus must-have skills (at least one independent-operator
   employee with that skill present in the block)

Core functions:
- Generate the weekly schedule draft: a people-by-block grid;
  click a cell to assign, remove, or swap; everything stays
  hand-editable - the tool drafts, the human decides
- Conflicts flagged red, four classes, with a legend:
  a skill gap: the block lists a must-have skill with no
    independent-operator coverage
  b over hours: someone's scheduled hours this week pass their
    cap (the number shows in the cell corner)
  c availability collision: scheduled into a block the person
    marked unavailable
  d short turn-around: the gap between someone's closing shift
    and next-day oven opening shift is under [minimum gap] hours
- Flag red only, never auto-resolve - no "fix it all" button:
  every scheduling trade-off is made by a human, and the tool's
  job is making invisible conflicts visible
- Weekly hours column per person, updating live with the grid;
  yellow within [margin warning] hours of the cap, red over it

Data and export:
- localStorage save, survives refresh; two actions: "clear this
  week" and "copy as next week's template"
- One-click copy as a plain-text weekly schedule (for sending to
  the staff group chat, aligned formatting; conflicts are not
  exported - the schedule sent out is a decision, not a
  discussion draft)

Interface constraints:
- Fits on one screen, type sized for a scheduling supervisor
  reading it on a phone
- No popups, no page navigation; every interaction completes
  inline

Why it is written this way

"Drafting board, not auto-scheduler" is the tool's whole positioning: scheduling is a mixed weigh of skill structure, personal favors, legal lines, and private lives. A fully automatic schedule looks like a time-saver and actually turns the supervisor into someone arguing with a black box. The tool drafts, the human clicks cells, and every change is an explicit decision - when a conflict blows up, it can be traced to who changed what and when, so the chain of responsibility stays clear.

Of the four conflict flags, "skill gap" and "short turn-around" are bakery-specific. The first is the live version of the auditor's "headcount enough, shift cannot open". The second is the bakery early shift's hidden mine: the oven-opening shift clocks in before dawn, the closing shift walks out at ten at night, and the same person scheduled on both shows up as two different cells on the grid while being one employee twenty hours without sleep. The minimum gap is a variable because shift structures differ shop to shop - hard-code a number and nobody trusts it.

No "fix it all" button is deliberate restraint: auto-fix would move several people's shifts at once, each move individually reasonable, and together they can shred one employee's rest days - a shredding only a human can see. Red flags turn problems into loud blocks, and the decisions stay with the person. That division of labor is the right responsibility boundary between tool and supervisor.

The group-chat export carrying no conflicts follows the same logic: the schedule posted to the staff group is the final decision, and the red flags are internal working material from the scheduling process. Send the discussion draft and the decision together, and what the staff see is not a schedule - it is their rest days being publicly debated.

Variables