how long until the thing.

Build me a countdown page as a single web page.

Ask me first:
- What the date is, and the time of day if it matters.
- What I am counting down to, and how it should be described on the page.
- Whether the countdown should use the visitor's local time zone or one fixed zone.
- What should happen when it reaches zero.
- The mood: celebratory, calm, stark, playful — and any colours or imagery I want.

Do not invent the date, the occasion, or details about it.

WHAT IT DOES

- Shows the number of days remaining as the dominant element on the page. If the date is within a few days, also show hours and minutes, updating live.
- Computes from the visitor's clock, in the time zone I specified. If I chose a fixed zone, say which one on the page so a visitor elsewhere is not confused.
- Handles the moment it hits zero exactly as I described, and keeps working sensibly afterwards rather than showing a negative number or NaN.
- Handles being opened months early and minutes late equally well.

DESIGN

- The number is the page. Everything else supports it.
- Build the design around the occasion I described rather than a generic dark-with-neon countdown.
- Readable on a phone in a message thread, which is where most people will open it.
- Include Open Graph and Twitter card tags with a title and description that make sense when the link is pasted into a chat.

BE HONEST ON THE PAGE

- Do not claim reminders, notifications or email alerts. The page cannot send anything.
- If the page stores nothing, there is nothing to disclose — do not add a storage notice that is not true.

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="countdown">

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