Hongming Wang ce88a396da fix(scheduler): #152 problem B — persist and surface cron error_detail ... Closes #152 problem B (schedule history API drops error detail). Two tiny changes: 1. scheduler.fireSchedule now writes lastError into activity_logs.error_detail when inserting the cron_run row. Previously the column was left NULL even on failure because the INSERT didn't include it. 2. schedules.History SELECT now reads error_detail and includes it in the JSON response under error_detail. Frontend + audit cron can now display "why did this run fail" instead of just "status=error". No schema change — activity_logs.error_detail already exists from migration 009. This just starts using the column. Problem A of #152 (Research Lead ecosystem-watch 50% error rate on its own) is a separate ops investigation and stays open. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-15 11:11:16 -07:00
..
scheduler_test.go	test(scheduler): add unit tests for Healthy, LastTickAt, ComputeNextRun, panic recovery	2026-04-15 07:42:13 +00:00
scheduler.go	fix(scheduler): #152 problem B — persist and surface cron error_detail	2026-04-15 11:11:16 -07:00