what is happening, and when.

Build me a running order for an event as a single web page, to send to everyone involved.

Ask me first:
- The event, the date, and what happens — in time order, with times.
- The locations, and how people get between them.
- Who is responsible for what, if that matters.
- Anything people need to bring, wear or know.
- Whether this is for guests, for the people running it, or both. Ask, because the detail level differs.

Include only what I give you. Do not invent timings, addresses, or a schedule of things that "usually" happen.

WHAT IT DOES

- The day in time order: each item with its time, what it is, and where.
- Travel between locations shown as its own item with how long it takes, so nobody has to work it out at the time.
- Names against responsibilities where I gave them.
- On the day itself, highlight the current item based on the visitor's clock, and make what is next obvious. This is the single most useful behaviour on the page.
- Addresses as copyable text with a plain link to a map search. No embedded map — it would break offline use.
- Print styles producing one clean sheet, because somebody always wants it on paper.

DESIGN

- Readable on a phone, quickly, possibly in the dark and possibly by someone who has had a drink. Large times, clear separation between items.
- Works with no signal once loaded. No external fonts, scripts or images.
- Say when it was last updated, so nobody follows a stale version.

BE HONEST ON THE PAGE

- Note that it works offline once opened, and suggest people open it before they set off.
- Do not claim notifications, reminders or live updates. Changes need a republish and people will see them next time they load it.

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="party-itinerary">

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