rabbitblood 3249d3ffdb fix(scheduler): detect phantom-producing crons via consecutive-empty tracking (#795) ... Post-mortem fix: UIUX Designer ran 22 cron fires over 23 hours with every single response being empty or '(no response generated)'. The scheduler reported status=ok because the HTTP call succeeded — nobody caught it until the CEO asked. Changes: - Migration 032: adds consecutive_empty_runs INT to workspace_schedules - scheduler.go: captures response body from ProxyA2ARequest (was _), checks for empty/sentinel markers via isEmptyResponse(), increments consecutive_empty_runs on empty ok responses, resets on non-empty. When consecutive_empty_runs >= 3, sets last_status='stale' with a descriptive error message. The 'stale' status is surfaced via: - GET /admin/schedules/health (merged in #671) - PM's silence detector (companion fix in org-template PR) - Maintenance loop response-body sampling (operator-side fix) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-17 11:11:05 -07:00
..
scheduler_test.go	test(hibernation): integration tests for workspace hibernation (#711)	2026-04-17 15:44:41 +00:00
scheduler.go	fix(scheduler): detect phantom-producing crons via consecutive-empty tracking (#795)	2026-04-17 11:11:05 -07:00