refactor(Where): retire AI recent activity summaries

[kyleve]

Posted by an AI agent on kve's behalf.

Summary

• User-facing: remove the AI Recent Activity summary from Your Year, Settings feature galleries, Siri, and Shortcuts
• Internal: delete the Foundation Models summarizer, public service API, logging, localization, previews, typewriter support, tests, and snapshot suite
• preserve the unrelated scheduled daily-summary notification and device-recording recency policy
• refresh the remaining Year, Insights & Accuracy, and Siri snapshot matrices and reconcile the backlog/docs

Why

The AI narrative was unreliable and not worth maintaining. Retiring it end to end avoids leaving a hidden App Intent, unused model infrastructure, or marketing copy for a feature the app no longer supports.

Review focus

• confirm the remaining Insights & Accuracy screen reads coherently as a Resolve/data-quality surface
• confirm the regenerated Year and Siri references remove the entry points without disturbing their remaining layout or accessibility output
• verify the daily notification recap remains untouched despite its separate use of “summary” terminology

⚠️ Breaking changes

WhereServices.recentActivity, its generator injection, the Recent Activity domain types, and RecentActivitySummaryIntent are removed without compatibility shims. Existing user-created Shortcuts that reference the retired App Intent will no longer run.

Compatibility

No persisted data, backups, CloudKit schema, or notification preferences change. The scheduled daily recap and RecordingOnboardingRecommendation.recentActivityWindow remain supported.

Testing

• ./test --all — 1,804 tests passed
• targeted ./test --snapshots --review for InsightsAccuracyFeaturesViewSnapshotTests, SiriFeaturesViewSnapshotTests, and YearViewSnapshotTests — 3/3 suites passed after recording and visual review
• ./swiftformat --lint
• ./xcstrings --lint
• ./snapshot-shards check — 41 suites balanced across the existing two shards
• git diff --check

The initial full snapshot traversal found unrelated references as unhydrated Git LFS pointers in this checkout, so those comparisons were reported as incomparable; the three affected suites were explicitly recorded, inspected in standard and accessibility configurations, and rerun successfully.