Curation v2 step 1: three-way feedback, rating events, reader profile

- Migration 0002: rating_events, article_embeddings, interest_embeddings,
  article_assessments, candidate_runs, runs.config_json/provider_costs_json,
  issue_articles.why; copies ratings into rating_events and drops ratings and
  feed_priors (scores stays until step 4).
- Vote is Loved | Good | NotForMe; legacy `up` links still verify as Loved.
- Footer offers Loved it / Good / Not for me; the confirmation page offers the
  other two so a mis-tap can be corrected. handle_rating appends one event.
- db::current_ratings implements the latest-explicit-event rule with summaries
  and facets; `ratings list|set|clear` CLI appends source='cli' events.
- data/profile.md replaces the hard-coded reader prose; the system prompt is
  rebuilt every run in the §8.4 order with a recent-verdicts block.
- Weekly rebuild reads summaries, facets and notes; feed priors removed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A1rCLQeKBgnBo3oTgHuTMe

data/profile.md

@@ -0,0 +1,30 @@
+# Reader profile
+
+## Who he is
+A software engineer in the Boston area who reads on e-ink in the morning. He would
+rather read six excellent long pieces than thirty adequate short ones. He reads across
+an unusually wide range of subjects and does not need a topic to be professionally
+useful to enjoy it.
+
+## What he wants
+- Long-form and high-effort above all: essays, deep dives, post-mortems, field notes,
+  annotated experiments, thorough explainers, personal narratives with real specificity.
+  Length is a proxy, not the goal.
+- Any topic, if the writing is excellent.
+- Social proof is evidence a critical audience read it, not a verdict.
+- Boston and New England local news: city government, transit, universities, civic stories.
+- Ultra-niche community news: small scenes with their own vocabulary.
+- World and US news kept light and neutral (the World Briefing covers it separately).
+
+## What he does not want
+Press releases and funding announcements dressed as news; SEO listicles; link roundups;
+changelogs without analysis; sponsored content; crypto and engagement bait; rewrites of a
+story he can read at the source; culture-war outrage; one paragraph stretched to five.
+
+## How to judge
+Would he still be glad he read this an hour later? Reward specificity, first-hand
+experience, honest uncertainty, and prose with a human behind it. Penalize padding,
+unsourced confidence, and summaries of other people's work.
+
+## Interests
+(optional: one per line; merged with data/scour-interests.opml)