somewhere plain to write it down.

Build me a private journal as a single web page. Everything stays in my browser.

Ask me first:
- Whether I want a prompt to write against each day, and if so what kind — or nothing at all.
- Whether entries are one per day or as many as I like.
- Whether I want to tag entries or note a mood, or keep it to plain text.
- Roughly how long my entries tend to be, so the writing area is the right size.

Do not invent journalling prompts of the inspirational-quote kind unless I ask for them. Do not invent entries.

WHAT IT DOES

- Opens on today, with the cursor in the writing area. Writing should be the first thing possible, before any navigation.
- Saves as I type, continuously, without a save button. Losing a paragraph because the tab closed is the one unacceptable failure.
- Shows today's prompt if I asked for prompts, in a way I can ignore.
- Yesterday and the last several days readable below, collapsed, in date order.
- An index by month once there are enough entries, and a plain text search across everything.
- Editing a past entry is possible but should take a deliberate action, not a stray tap.

BACKUP — TREAT THIS AS A FEATURE, NOT A FOOTNOTE

- A prominent export that downloads or copies everything as JSON, and also offers plain text or markdown.
- An import that restores from that file.
- On the page, in normal-sized text: entries are stored in this browser only, there is no copy anywhere else, and clearing site data will delete them permanently. Suggest exporting periodically.

DESIGN

- Calm. Generous line height, comfortable measure, nothing flashing while I write.
- Works on a phone and on a laptop; most people write on one and read back on the other.
- Do not add word-count pressure, streaks, or "you have not written in 3 days" messages.

BE HONEST ON THE PAGE

- Say plainly: stored in this browser, not encrypted, not synced, not sent anywhere.
- Do not describe the journal as secure or private beyond what that sentence supports — anyone using this browser profile can read it.

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="personal-journal">

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