Naiyuan Qing b8fa71462a fix(subscribers): pass user_type to subscribe/unsubscribe API for correct agent handling ... Root cause: backend hardcoded UserType="member" in subscribe/unsubscribe handlers, so unsubscribing an agent actually tried to delete a member record (no-op), and the WS event broadcast wrong user_type causing other subscribers' UI to break. - Backend: accept optional user_type in subscribe/unsubscribe request body - Frontend: pass userType through API client to backend - Fixes: clicking agent checkbox no longer affects member subscriptions Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-28 20:56:37 +08:00
..
cmd	fix(notifications): address code review feedback	2026-03-28 20:24:07 +08:00
internal	fix(subscribers): pass user_type to subscribe/unsubscribe API for correct agent handling	2026-03-28 20:56:37 +08:00
migrations	fix(notifications): address code review feedback	2026-03-28 20:24:07 +08:00
pkg	feat(notifications): replace hardcoded inbox notifications with subscriber-driven model	2026-03-28 19:33:20 +08:00
go.mod	feat(auth): email verification login and personal access tokens	2026-03-26 14:32:30 +08:00
go.sum	feat(auth): email verification login and personal access tokens	2026-03-26 14:32:30 +08:00
sqlc.yaml	feat: pivot to AI-native task management platform (#232)	2026-03-20 17:55:49 +08:00