feat: always-on Insights — correlation analysis over viewing habits

Conservative, live insights (ADR-0010) derived from each user's diary:
rating lift by genre (first-time watches only), genre seasonality vs a
uniform 1/12 month baseline, medium weekend-lift, and watch-time rhythm.

- domain: WatchRow model, InsightsQuery port, pure insights_analyzer with
  all honesty thresholds (sample minimums, strength cutoffs, suppressions
  for import noise), unit-tested
- adapters: thin Sqlite/Postgres fetch twins, reusing WrapUp's genre fetch
- application: get_insights use case, InsightsGroup in Deps
- composition/server: wiring through Repositories/DatabaseOutput
- presentation: GET /api/v1/insights handler, typed serde-tagged DTOs,
  openapi doc
- spa: /insights route (shadcn cards), insights feature hook, profile
  entry link, en locale strings
- server test: end-to-end seed sqlite → HTTP → rating lift + rhythm

Also records ADR-0010, defines "Insight" in the glossary, and includes
pre-existing worktree comment-stripping cleanups.

crates/presentation/src/handlers/social.rs

@@ -1104,9 +1104,6 @@ mod tests {
         }
     }
 
-    /// The bug: a local actor used to serialize as `local:{uuid}`, which
-    /// `identify` cannot parse, so every POST echoing this url back resolved
-    /// to Remote and was routed to ActivityPub.
     #[test]
     fn local_actor_dto_url_round_trips_back_to_the_same_identity() {
         let instance = InstanceIdentity::new("https://md.example");