F8: Event Tracking Core Schema
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 7
- Avg merge
- 20h 35m
- Merged PRs (30d)
- 66
Description
## Summary
Foundational event tracking covering deploy funnel, upgrade-prompt interactions, and diagnosis/recommendation outcomes. Required before any monetization or fault detection can ship meaningfully.
## Acceptance Criteria
- [ ] Core event schema defined and implemented
- [ ] Deploy funnel events captured
- [ ] Monetization event stubs from day one
- [ ] Diagnosis event stubs from day one
- [ ] Upgrade-prompt interaction events
## Sprint Assignment
- Sprint 1: Background work (ships as infrastructure, not user-facing)
## Notes
- Shared dependency for all four capabilities
- Must be in place before Monetization MVP (Sprint 2)
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating existing event-tracking or telemetry code in the repository and identify how deploy, monetization, diagnosis, and upgrade-prompt events should share a schema. Done means the core schema and all listed event captures or stubs are implemented and verified by the project’s relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100