plan it before you are standing in it.

Build me a trip planning page as a single web page. This is for while the trip is still being decided, not the final itinerary.

Ask me first:
- Where I am going, roughly when, and for how long.
- Who is travelling.
- How the trip breaks up — legs, cities, days, or something else.
- Whether I want a budget tracked, and in which currency.
- What is already decided and what is still open.

Do not invent destinations, prices, hotels, or recommendations about where to go. If I have not told you something, leave a clearly marked gap.

WHAT IT DOES

- Structures the trip the way I described — legs, or days, or both — with each part showing what is settled and what is not.
- Keeps decided and undecided visibly separate. Undecided items list the options I am choosing between, with a cost against each, so the comparison is on the page rather than in my head.
- A running budget: what is committed, what is estimated, and the total under the current choices. Update it as options are chosen. Make clear which figures are estimates.
- An outstanding list: what still needs booking, and anything with a deadline attached.
- A place for links and references — the booking pages, the places I have read about — as plain links.
- Let me mark an option chosen, which moves it into decided and updates the budget.

DESIGN

- A working document. Dense is fine; this is read on a laptop while planning.
- Should still be readable on a phone, since half of planning happens in bed.
- No imagery, no destination photographs, no travel-brochure styling.

BE HONEST ON THE PAGE

- Say notes are stored in this browser only, so sending the url to someone shows them the page, not my planning.
- Do not claim live prices, exchange rates, availability or weather. There are no network requests.
- Do not recommend destinations or activities I did not mention — this is my trip, not a suggestion engine.

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