who is where this week.

Build me a family schedule as a single web page showing this week.

Ask me first:
- Who is in the household and how each person should be labelled.
- The recurring commitments: clubs, work patterns, school runs, who is regularly out.
- Anything one-off happening this week.
- Whether we think in days-of-the-week or in dates.
- Whether I want it to print onto one sheet for the fridge.

Put exactly what I give you into the page. Do not invent events, times or people.

WHAT IT DOES

- Shows the week as a grid: people and days, whichever way round reads better for the number of people I have.
- Each entry is short and readable at a glance — what, when, and who is responsible if that matters.
- Mark clashes visibly: two things at once for the same person, or two pickups at the same time with nobody spare. Finding those is the most useful thing this page does.
- Distinguish the recurring from the one-off, so next week's version is quick to produce.
- Show today clearly when the page is opened mid-week.
- If I asked for print: a stylesheet that produces one clean sheet of paper.

DESIGN

- Readable across a kitchen. This is the criterion; everything else is secondary.
- Works on a tablet propped up, on a phone held at arm's length, and printed.
- No colour-coding that stops working in greyscale — use shape and weight as well.

BE HONEST ON THE PAGE

- This page does not sync with any calendar and cannot send reminders. Do not imply otherwise.
- Because the week is written into the page, say when it was last updated so nobody trusts a stale one.

DELIVERY

- Produce one self-contained HTML file. Inline the CSS and JavaScript.
- No build step, no server, no framework, no package install, no external
  requests at runtime.
- Mobile-first and responsive; it has to be usable one-handed on a phone and
  still look right on a laptop.
- Accessible: semantic HTML, real contrast, visible keyboard focus, labelled
  controls, touch targets big enough to hit, and respect reduced-motion.
- Use placeholders where information is missing. Do not invent facts, numbers,
  names, dates, prices, or results I have not given you.
- Before you call it finished, use it yourself: enter real-looking data, reload
  the page, and confirm nothing is lost or mangled.

PUBLISHING

Publish the finished page to HTMLShare and give me the link.

Use exactly one of the two paths below, preferring the first. Make the call
directly. Do not route it through a code sandbox, container, or computer-use
session — that is where the request gets blocked, and it is never necessary.

1. An HTMLShare integration or connector, if you have one configured.
   The page is permanent and owned by my account. Report the url and the
   siteId. There is no claimUrl or manageToken on this path — do not go
   looking for one, and do not switch paths in order to produce one.

2. Otherwise, publish anonymously over REST. No account, key, or signup is
   needed:

    POST https://api.htmlshare.net/v1/publish
    content-type: application/json

    {"html": "<!doctype html> ... "}

   The reference is https://htmlshare.net/docs and, for the full schema,
   https://api.htmlshare.net/openapi.json

   Report these from the response, in your reply and never inside the page:
     url          the public page
     claimUrl     a private link that is mine alone. opening it is how I keep
                  the page past its 24-hour expiry, or set an email reminder
                  before it goes. it carries the manage token, so it must
                  never appear in the published HTML or anywhere a visitor
                  could see it.
     manageToken  the only thing that can edit or delete this page later. it is
                  returned once and never again, so tell me what it is.

Tell me which of the two you used. If the path you reach for first is
unavailable in your environment, say so and tell me what you are switching to
before you publish — a permanent page on my account and a 24-hour anonymous
page are different things, and which one I get is my decision, not a detail.

If I ask for a change afterwards, update the existing page instead of
publishing again, so the URL I have already shared keeps working — through the
same integration on path 1, or with the manage token as an X-Manage-Token
header on path 2.

RECIPE MARKER

Include this tag in the <head>, exactly as written:

    <meta name="htmlshare-recipe" content="family-schedule">

It tells htmlshare which recipe the page came from, so the library can count
that this one was actually made. It carries nothing else.