## Summary Set up `connection_event` and `hackathon_attendance` tables. ## Contexts Foundation for both streak types. Receiver privacy rule: receiver_id only stored with consent. ## Tasks - [ ] Create `connection_event` table per spec - [ ] Create `hackathon_attendance` table per spec - [ ] Enforce receiver_id is only ever set when receiver is signed in and consents ## Acceptance Criteria - [ ] Migrations run cleanly - [ ] Anonymous connections never write a receiver_id - [ ] Tests added - [ ] docs updated ## Area `backend` ## Difficulty Good first issue
Summary
Set up
connection_eventandhackathon_attendancetables.Contexts
Foundation for both streak types. Receiver privacy rule: receiver_id only stored with consent.
Tasks
connection_eventtable per spechackathon_attendancetable per specAcceptance Criteria
Area
backendDifficulty
Good first issue