- logr README: restructure the Vitals + Sentry section into two clearly
separated delivery paths. Path A (via the logger → sentryTransport)
reaches Issues/breadcrumbs; Path B (via Sentry's browserTracingIntegration)
reaches the Performance/Insights product. Add a decision table covering
the five common use cases (aggregate dashboards, triage breadcrumbs,
alerts on poor ratings, non-Sentry backends, dev validation) with the
recommended path for each, and document the production combo of Path B
for analytics plus Path A at `breadcrumbLevel: TRACE` for error-context
breadcrumbs.
- Test page: enable Sentry.browserTracingIntegration() with
tracesSampleRate=1.0 so the page load emits a real transaction visible
under Insights → Browser → Web Vitals, in addition to the logger-based
vitals that already land as Issues. Promote every vital rating to ERROR
in the test page override so good/needs-improvement samples also surface
in the Issues feed — useful to validate end-to-end.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dev
342e189244