doot.git/internal/store/native_tasks_test.go, branch masterdoot — personal productivity web app
https://git.terst.org/doot.git/atom?h=master2026-07-12T05:36:32+00:00fix(widget): surface unmatched task IDs instead of silently no-opping2026-07-12T05:36:32+00:00Peter Stonethepeterstone@gmail.com2026-07-12T05:36:32+00:00urn:sha1:9a87f9db5af943ea253b814d4196020341e3c2ba
CompleteNativeTask/UncompleteNativeTask/RescheduleNativeTask ran a plain
UPDATE ... WHERE id = ? and returned whatever error Exec gave back --
which is nil even when 0 rows match, since that's not a SQL error. A
stale or wrong id from the widget looked identical to a real completion:
HTTP 200, nothing changed in the database. Real incident: 1 of 3 widget
completeTask taps silently no-opped this way.
Now checks RowsAffected() and returns ErrNativeTaskNotFound (mirrors the
existing pattern in sqlite.go's ApproveAgentSession/DenyAgentSession).
HandleWidgetComplete and HandleWidgetReschedule surface this as 404
instead of a fake 200, so the widget can tell 'nothing changed' apart
from 'it worked.'