Tell the user their run expired instead of showing a blank form

[ThinkingSpade]

Tell the user their run expired instead of showing a blank form

Follow-up to #34 and #35, closing the rest of the restore-layer findings.

THE PROBLEM

hydrate returned RestoredRun | null, and that single null meant three
completely different things:

• there is no past run for this tab
• there IS a run and its stored result is gone
• there is a run and its result no longer matches this tab's schema

Callers rendered all three as the tab's ordinary "you have never run this"
empty state. So the middle case -- by far the most common, because run payloads
lived under a prefix Cloudflare deletes after 7 days (see #34) -- looked exactly
like a tab you had never opened. That is the same error-as-absence antipattern
this codebase eliminated in its query layer, still living in the restore layer.

THE CHANGE

hydrate now returns a discriminated RestoreOutcome:

{ status: "none" }
{ status: "expired", label, lastRanAt }
{ status: "ready", run }

The row itself is the proof: if a row exists but the payload does not, that is
an EXPIRY, not an absence, and it can be said out loud. useAutoRestoredRun
surfaces this as outcome plus an expired bundle, and Domain Overview's
empty state now explains itself rather than pretending the tab is fresh.

unreadable (schema mismatch) is reported too. It was the most dangerous of
the three: a schema change would have silently stopped every stored run from
restoring, with nothing anywhere to indicate it.

ALSO FIXED IN RecentRunsList

• query.data ?? [] hid the whole history section on a failed fetch, so a
  transport error read as "you have only run this once". Now offers a retry.
• Selecting a run swallowed failures with .catch(() => undefined), leaving a
  button that appeared to do nothing when clicked. Now marks the row.
• Its existing restored == null expiry check would have SILENTLY BROKEN under
  the new return type -- null is no longer reachable, so the check would
  always be false and an expired run would look successful. Updated to test
  status. Flagging it because tsc could not catch it: the comparison stays
  legal, it just stops being true.

useLastRunInput reads the new shape as well; it only wants a prefill value
and has nothing to say about expiry, so both non-ready cases stay null.

VERIFICATION

pnpm ci:check clean; 2,129 tests passing across 224 files; tsc clean.

NOT DONE, and deliberately not rushed:

• The Local SEO city picker. Diagnosed fully -- the server already accepts
  locationCode (default 2840, the whole United States) and the client never
  sends it, which is why the UI tells users to type a city into the business
  NAME field. The fix needs that code threaded into the query key AND the
  metered authorization key; get the second one wrong and changing city fires a
  paid lookup with no click. That is the one class of bug this project guards
  hardest against, so it wants a fresh session, not the tail of a long one.
• D1 prune, so rows do not outlive the 90-day payload the way they outlived the
  7-day one.
• content_brief's separate defect (a 2-day-old payload already missing).

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	flyrocketseo	2ebe0aa	Aug 05 2026, 08:33 AM