4 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 4.8	a1a5217d77	feat(web): honest sparse-state and queue copy ... Make the sparse reality legible instead of implying abundance or imminence (UX review A1-A4, A6): - Empty-connected state drops the impossible "Run `tapir run`" instruction (no shell for web users; discovery is in-process since ADR-018) for a passive "summaries appear gradually, check back later". - Pipeline bar reframes counts by what the user can do: "N ready · M in queue · K no captions" (was "summarized / fetching soon / pending"). - A one-line note explains captions are fetched slowly on purpose to respect YouTube's limits — turning confusing emptiness into intentional design. - Card state for throttled videos reads "In queue", not "Fetching soon…" (256 items behind a per-IP gate are not all imminent — ADR-014). - Quiet nudge button drops the over-promising "now": "Summarize", not "Summarize now". On click the card still honestly becomes "Queued". - Queued card says "summarizing shortly", not "waiting for the next run" (no scheduler jargon). Pure copy/label — no logic, DB, or fetch-rate change. The rate gate is untouched; scarcity is surfaced, never engineered around. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-08 13:42:40 +02:00
mathias	2fedc45443	feat(web): unify card states — one 'Summarize now' verb, honest no-captions state ... Five explicit footer states, status-primary: 1. Summarized — chip + actions, no button (unchanged) 2. No captions (TranscriptStatus=="none") — NEW: 'No transcript available' muted text, no button, no POST URL. Removes the dead-end 'Summarize' button that tried and failed when there were no captions to fetch. 3. Queued (SummarizeRequested) — chip + muted text, no button (unchanged) 4. Rate-limited — 'Fetching soon…' + quiet 'Summarize now' → /retry-now 5. Pending — 'Not summarized' + quiet 'Summarize now' → /summarize One verb ('Summarize now'), one quiet style (.btn-quiet, renamed from .btn-retry which was state-specific). User doesn't see the internal pipeline distinction; both buttons post to their existing handlers unchanged. Form class renamed card-nudge-form. Dropped engineer-facing tooltip; user-facing hint added. 'Try now' wording removed entirely.	2026-06-06 22:31:41 +02:00
mathias	57e29ca06c	feat(web): pipeline stats bar, summarized-first sort, Try now button for rate-limited videos ... Three UX improvements for the pending-transcript state: 1. Summarized videos sort to top (ORDER BY (s.id IS NOT NULL) DESC, seen_at DESC) so completed summaries are always immediately visible without filtering. ListVideos default limit raised from 50 to 500 to show the full backlog. 2. Pipeline stats bar above the video list: '2 summarized · 256 fetching soon · 12 no captions' — computed from the unfiltered row set, hidden when everything is summarized. 3. 'Try now' button on rate-limited cards replaces the passive 'Retrying later' chip. POST /v/{id}/retry-now clears rate_limited_at then calls ProcessVideo through the shared globalFetchGate — same rate limiting as the scheduler, safe under concurrent use.	2026-06-06 19:20:20 +02:00
mathiasandClaude Opus 4.8	943554a96c	feat(web): "Retrying later" badge for rate-limited videos ... A discovered-but-unsummarized video whose caption fetch was rate-limited now shows a passive ⏳ "Retrying later" chip (dim CharmDim styling, not the accent) instead of the Summarize button — the user cannot fix a 429, the runner retries automatically once the backoff window expires. Regenerated views_templ.go. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 22:56:48 +02:00