Part of epic: #209
[Platform: App, Web, Studio]
Context
The user profile has no tradition field. POST /users/info and GET /users/info both exist but carry no tradition data. This is a schema addition to an existing endpoint — no new API path needed.
Why This Matters
The app needs to remember which traditions a user practices so it can filter content accordingly. Like language preference, this needs to be stored server-side — not locally — so it persists across devices and reinstalls.
Acceptance Criteria
Flags
- ⚠️ Schema migration — existing user records will have no
traditions value; treat null/missing as "All Traditions"
Part of epic: #209
[Platform: App, Web, Studio]
Context
The user profile has no tradition field.
POST /users/infoandGET /users/infoboth exist but carry no tradition data. This is a schema addition to an existing endpoint — no new API path needed.Why This Matters
The app needs to remember which traditions a user practices so it can filter content accordingly. Like language preference, this needs to be stored server-side — not locally — so it persists across devices and reinstalls.
Acceptance Criteria
traditionsfield (list of strings) added toUserInfoRequestschema — accepted byPOST /users/infotraditionsfield added toUserInfoResponseschema — returned byGET /users/infotraditionsfield is valid — treated as "All Traditions" (no filtering)theravada,pure_land,zen,tibetan,ambedkar,general— invalid values should be rejectedFlags
traditionsvalue; treat null/missing as "All Traditions"