Commit graph

3 commits

Author SHA1 Message Date
Arlind Ukshini
44f7a8c5d7 docs: implementation plan for engagement event tracking
9 tasks: schema → CLI → UA parser → wire UA into server → recorder
→ issueSession refactor → login event → timeline_view event → docs.
Each task is a self-contained commit with verification steps using
curl + the new events CLI (no test framework on this project).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 10:08:19 +02:00
Arlind Ukshini
4d2ff042e3 docs: drop welcome_cta event from engagement tracking spec
There's only one welcome-step button (#welcome-continue, label "Start
the introduction"); the recent renames were sequential edits to the
same button, not two separate CTAs. The click immediately navigates to
/timeline so the subsequent timeline_view event already captures it.

Also clarified GET / no longer has a timeline branch, and pinned down
how session_id flows into the login event (refactor issueSession to
return its new ID).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 10:03:53 +02:00
Arlind Ukshini
9044573d01 docs: spec for engagement event tracking
Server-side landmark events (login, welcome_cta, timeline_view) into a
unified events table with device fields. CLI-only readout via
bin/events.js. bifrost_joins left in place.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 09:53:48 +02:00