Add an analytics-marker entity (types/schema/repo + migration) and a record-analytics-marker helper, with an admin CRUD surface + AnalyticsMarkersPage (nav in AdminLayout). Auto-record markers when tour stops and content drops are created/changed. Expose them via /analytics/markers (analytics-queries + user-data router proxy + useMarkers hook + api types), and render them as reference lines with a legend on the dashboard Overview trend chart. |
||
|---|---|---|
| .. | ||
| backend-api | ||
| frontend-public | ||
| mcp-server | ||
| shared | ||