4 Commits

Include renames

Author	SHA1	Message	Date
mathias	f1e9739900	feat(store,runner,web): channel unavailability notice (migration 013) ... YouTube channels that 404 on playlist discovery (deleted/private) are now: 1. Wrapped in domain.ErrChannelUnavailable by the YouTube adapter (instead of a generic error), so the runner can identify them without string-matching. 2. Stored per-user in channel_errors (migration 013, RLS-guarded) via runner's new UpsertChannelError path — removed from the generic Errors counter, counted separately as ChannelUnavailable. 3. Shown on the account page under "Unavailable channels" with name, chip-warn badge, and first-seen date, so users know why some subscribed channels produce no videos.	2026-06-06 10:09:52 +02:00
mathias	940f80899a	fix(store): migration 012 — back-fill auto_summarize via RLS bypass ... Migration 011's UPDATE ran without tapir.current_user_id set, so FORCE RLS blocked all rows and 0 users were updated (skipped_manual=607 in scheduler). Migration 012 temporarily drops FORCE so the table owner can run the UPDATE, then restores it.	2026-06-06 10:01:13 +02:00
mathiasandClaude Opus 4.8	5d029a2823	feat(store): default auto_summarize ON for new users (ADR-018) ... Migration 011 flips the auto_summarize column default to TRUE and brings existing rows (maintainer + current registrations) along. Onboarded friends now get zero-friction discovery: scheduled discovery (ADR-018) both discovers AND summarizes new videos, so a user's list fills and summarizes itself instead of presenting an empty list of manual Summarize buttons. Safe only because the process-wide caption-fetch rate gate (ADR-014 item 2, prior commit) now exists — auto + scheduled + multi-user would otherwise self-inflict 429s every cycle. The down migration reverts the default but intentionally leaves existing rows as-is (no surprise manual regression on rollback). RegisterUser already lets the column default drive the value, so no app change is needed; the account-page manual toggle still works. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-05 23:42:23 +02:00
mathiasandClaude Opus 4.8	b070347597	feat(store): add append-only login_events table with forced RLS ... Stage-0 usage measurement (VISION/ADR-016): summary_actions captures acts (watch/skip/save) but not reads. A reader who logs in weekly and clicks nothing is invisible — for a reading product that return is the signal the gate ("usage in >=2 distinct weeks") is defined on. login_events records THAT a user was active, append-only, one row per user per active day. Per-user isolation via the same GUC-keyed FORCE RLS policy as migration 003. No FK to users (mirrors summary_actions) — the cascade footgun is handled by DeleteUser in a later commit. Adds an up/down reversibility test and registers the table in both truncate helpers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 23:46:03 +02:00