b5ffab7ece
Release / release (push) Successful in 59s
Creating or updating a command tracker failed with 404 "Command config not found" when the selected config was a system default (seeded with user_id=0). The LIST endpoint already accepts both owned and system-shared rows via or_(CommandConfig.user_id == user.id, CommandConfig.user_id == 0) so the frontend legitimately offered a user_id=0 option — the POST and PATCH handlers then rejected it. Align the create/update checks with the list behavior: config.user_id not in (user.id, 0)