v1.17 wrap-up: performance, visits, source-map hardening — and what should AI summaries do?

[unjica]

The v1.17.x line (Performance Intelligence) has shipped. Here's a recap, then one question.

Shipped in v1.17.x

• Performance / Web Vitals views, compare periods, slow routes and pages
• Visits page: visitors, time on site, screens/actions, country, platform, browser and OS breakdowns (1.17.15)
• /pricing page on the site (1.17.17)
• Source map uploads now require a key with Allow source map uploads enabled. Ingest-only keys are rejected, and existing keys keep working so CI doesn't break. If a key is embedded in a client app, rotate it and create a separate CI key (1.17.18)
• Next.js 16 Turbopack: the Vite plugin and GitHub Action now derive bundle_url from sourceMappingURL, so maps symbolicate even when the chunk and map hashes differ (1.17.18)
• @telemetry-tracker/next 1.3.1 on npm (1.17.19)

Full notes: https://github.com/Telemetry-Tracker/telemetry-tracker/blob/develop/CHANGELOG.md

Next: v1.18 (AI Intelligence), grounded AI summaries
Before building it, I'd love input: what would you want a summary to tell you? Some candidates:

1. "What's new or worse since the last release"
2. A plain-language explanation of one error group
3. A daily or weekly digest of what needs attention

Reply with the one you'd actually use, or something better. If you self-host, tell me too, since that affects how this should work.