decide once, eat all week.

Build me a weekly meal planner as a single web page.

Ask me first:
- The meals my household actually cooks, as many as I can list. This is the most important answer.
- Roughly what ingredients each one needs, if I know them — I can fill gaps later.
- How many people I am cooking for, and whether that changes during the week.
- Anything nobody here will eat.
- Whether I plan dinners only, or other meals too.

Build from my answers. Do not invent recipes, do not add meals I did not name, and do not import anything from anywhere.

WHAT IT DOES

- A week grid: the days, each with a slot per meal I plan. Assigning a meal means picking from my bank, not typing it again.
- A meal bank listing everything I cook, with its ingredients. I can add to it, edit it, and add a meal straight into the week and into the bank in one action.
- A shopping list generated from the week's plan: every ingredient from every planned meal, combined where the same thing appears twice, grouped sensibly, and editable before I shop — I will already have half of it.
- A note of when each meal was last planned, so I can see the rotation collapsing before it does.
- Space for honest entries: leftovers, takeaway, "out". These are part of a real week and should not be missing from the page.
- Let me clear the week and start the next one without losing the bank.

DESIGN

- The week is the page on a laptop; on a phone, one day at a time with the week reachable.
- Picking a meal should be two taps. If it takes a form, this page will not survive a month.
- Plain and quick to scan. This gets read at a counter while something is boiling.

BE HONEST ON THE PAGE

- Say the plan and the meal bank are stored in this browser only, so another person in the house opening the same url sees their own empty copy.
- Do not add nutrition information, calorie counts or dietary advice.
- Do not claim to import recipes from websites. It cannot.

STORING THE DATA

- Save everything to localStorage in the browser, automatically, as I go. No
  accounts, no login, no server call.
- On the page, say plainly that data lives in this browser only and does not
  sync to other devices. Do not bury it.
- Give me an "export" button that copies or downloads everything as JSON, and an
  "import" that reads the same JSON back. That is the only way my data can move
  between devices, so it is not optional.
- Never lose what I have already entered. If the stored data is from an older
  version of the page, read what you can rather than throwing it away.

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="meal-planner">

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