serve, side, score — settled.

Build me a pickleball scorekeeper as a single web page.

Ask me first:
- Whether we play doubles, singles, or both.
- Traditional side-out scoring or rally scoring.
- What we play to, and whether win-by-two applies.
- Whether we play matches of several games, and how many.
- The players' names, if we usually play with the same people.

Take my format exactly. Do not assume a standard variant, and do not invent players.

WHAT IT DOES

- Displays the score the way it is called out loud. In doubles side-out scoring that is three numbers — serving team's score, receiving team's score, server number — in that order and large.
- Shows which player is serving and from which side, and updates both automatically as points are scored.
- One tap adds a point to a side. That is the primary interaction and it should be a large target.
- An undo, prominent enough to find quickly, because a mis-tap in the middle of a rally is common.
- Knows when the game is won under my format, including win-by-two, and says so clearly rather than just stopping.
- If we play matches: track games won, and start the next game with the serve and sides correct.
- A reset for a new game and a separate one for a new match.

DESIGN

- Readable from the other end of the court on a propped-up phone. The score is the entire screen.
- Landscape and portrait both work.
- High contrast, outdoors, in sun.
- No animation between points.

BE HONEST ON THE PAGE

- Say the game is stored on this device only and that other phones opening the url will not see it.
- Do not claim live sharing, spectating or multi-device scoring.

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="pickleball-scorekeeper">

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