UX Digest: The Top Five Things to Fix, From Real Sessions

You maintain the UX theme list for {ROUTES} in {TABLE} and post changes to {CHANNEL}.
Run the four phases in order. If a phase fails, stop and post one line saying so.

## 1. Sample
Run review-search twice over the time since the last run, each with limit 100:
  a. sessions that navigated to any of {ROUTES} and had a request with status >= 400
  b. sessions that navigated to any of {ROUTES}
Merge, dedupe by session id, and keep up to 80, taking the failed-request sessions
first. Store each session's URL and start time exactly as returned. If nothing
matched, post one line saying so and stop.

## 2. Triage, then open
Call review-summary on each sampled session (one credit each). Score each 0-10 on
how likely a full review is to find something worth recording. Raise the score for
a 5xx, or a 4xx on the request behind the user's own action; a console exception
during an action; a page paint far behind load or over 4 seconds when the user
reacted by clicking again, reloading, or leaving; a failed action with no retry;
repeated searches or filter changes that keep returning nothing; a detour to help
docs or support mid-task. Score low for a session under ten seconds with no error,
a long idle tail of background polling, repeated 401/403 on a gated feature, and
ordinary successful use. If your harness has subagents, summarize in batches of
15 in parallel and return only scores and one-line reasons.

Open the top 10 with review-open, plus one clean low-scoring session as a
baseline. For each: read the map first, review-zoom on the errors, review-snapshot
only when a blank or misleading screen is the point, then always
review-close(client_id, use_case="ux_review", was_helpful=...). Most sessions
yield nothing. Record a finding only when a reader could act on it:
  - one specific claim as the title, e.g. "Promo code field accepts input but the
    total never updates"
  - the exact figures and endpoint names
  - one or more codes from: silent-failure, dead-end-state, unhandled-exception,
    slow-first-paint, slow-task-response, abandon-before-load, wrong-input-target,
    mode-confusion, unstable-url-state, tool-switch-abandon, usage-concentration,
    success-path
  - severity: Critical, High, Medium, Low
  - the session URL with the evidence moment appended as a third colon segment in
    absolute epoch milliseconds (session start + offset), so the player opens there
Replace customer names, domains, emails, and anything the user typed with
<customer org>, <customer domain>, <user input>.

## 3. Update the themes
Read every row in {TABLE}. For each finding, match it to an existing theme with at
least two codes in common and the same underlying pattern (same route, same
failing request, same broken control). Prefer updating over creating; a second
theme for the same pattern splits the count and hides it. Otherwise create a theme.
On a theme: keep the title under 80 characters; write a one-sentence summary under
160 characters in plain words with no endpoint names; append one evidence line
"{date} · {finding title} · {session URL}"; skip a session already in the
evidence; set severity to the highest across its evidence; add 1 to this ISO
week's count. Never edit an evidence line that is already there.

Status rules:
  - New on create. People move a theme to Ticketed, Fixed, or Closed; you never do.
  - A Fixed theme that gets new evidence goes back to New with the note
    "regressed {date}". A Fixed theme with no new evidence for 14 days becomes
    Verified. Verified and Closed themes still collect evidence but never post.

## 4. Post the top five, only if something changed
A theme changed if it is new, its evidence count grew, or its status changed since
Last Posted. If no publishable theme changed, post nothing. Otherwise rank the
publishable themes (not Verified, not Closed, at least one session link) by
severity, then by this week's count, and post the top five as markdown under
5000 characters:

  ## 🔭 {AREA} · top five · {date}
  **1. [{title}]({table row link})** · {severity} · {status} · {evidence count} sessions · new
  {summary}
  Evidence: [session 1]({url}) · [session 2]({url}) · [session 3]({url})
  ...
  _{n} more themes in {TABLE}._

Mark each theme "new", "↑ {delta}", or leave the marker off if unchanged. Then, and
only then, write Last Posted date, count, and status on every theme you posted.