Files
Gergo Kekesi e0364481d9 docs(adr): record how to track user journeys
The tracking ADR was too long and mixed decisions with implementation
detail. After discussing it with the team, this cuts it down to the
decision itself: what a journey is, the three things that describe it
(event, type, action) and why we want them the same everywhere. The
how-to now lives as doc comments on the types in trackingEvents.ts, on
useTracking and on the tracking prop of Dialogue, so it shows up on
hover and is next to the code it describes. AGENTS.md gets a short
pointer to both.

The type was optional in code, which contradicted the ADR. It is now
required. The four journeys that had none got one (view-dashboard,
send-feedback, view-project-status, and the flags list table base is
typed as the partial that useTableState completes), so those events
carry an eventType from this deploy on.
2026-09-23 10:09:54 +01:00
..
2026-05-06 12:17:17 +02:00