the wedding, on one working page.

Build me a wedding planning page as a single web page. This is my working document, not the page guests see.

Ask me first:
- The date, if it is set, and roughly how far out we are.
- The budget, overall and whether I want it broken into categories.
- Which suppliers are involved or still to book — venue, catering, photography, music, whatever applies.
- Whether I want to track payments and deadlines.
- What is already decided and what is still open.
- My currency.

Do not invent suppliers, prices, traditions, or a checklist of things a wedding "should" have. Use what I tell you.

WHAT IT DOES

- A budget section: each line with what I planned and what I have actually committed or paid, the difference, and a total. Make the gap between planned and actual obvious — it is the number that surprises people.
- Suppliers: name, what they are for, what stage we are at (enquiring, quoted, booked, paid), what it costs, and what is owed when.
- Deadlines in date order, with anything overdue at the top.
- An open decisions list: what still needs deciding, and what it is waiting on.
- Guest numbers as counts and categories, not a list of names. If I ask for a guest list, keep it in the same local storage as everything else and warn me that any names typed into the page are still on my device only.
- Let me mark things done, and keep them visible rather than deleting them.

DESIGN

- Dense and practical. This is used on a laptop, often late, often tired.
- Numbers aligned and formatted consistently.
- Calm. No countdown pressure, no wedding-industry styling, no checklist of things I have not done.

BE HONEST ON THE PAGE

- State clearly and near the top that everything entered is stored in this browser only and that the published url shows nobody else any of it.
- Say that this is the planning page, and that anything for guests should be a separate page whose content is actually in it.
- Do not claim supplier directories, price benchmarks, or any outside data. There are no network requests.

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="wedding-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.