8bd00bb94a
Postgres TEXT columns in a UTF-8 database reject raw bytes like 0x80 and 0xff. The test was trying to insert these into workspace_schedules.prompt via insertSchedule, which failed with: pq: invalid byte sequence for encoding "UTF8": 0x80 Fix: insert a valid prompt into the DB fixture, then call fireSchedule directly with a scheduleRow whose Prompt field carries the invalid bytes. This still exercises the #2026 regression path (sanitizeUTF8 before jsonb INSERT) without tripping Postgres TEXT validation. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>