[daily-ai-review] Database schema error preventing source candidate persistence

[github-actions]

A database schema mismatch is preventing the persistence of source discovery data, indicating a potential deployment sync issue.

Error:

HTTPStatusError: Client error '400 Bad Request' for url 'https://ltafdcsnvppvqyoclkod.supabase.co/rest/v1/discovery_runs?on_conflict=run_id'
response_body={"code":"PGRST204","message":"Could not find the 'skipped_query_count' column of 'discovery_runs' in the schema cache"}

Impact:

• Source native candidate persistence is failing
• Potential data loss for discovery run metadata
• May affect historical tracking and analytics

Next steps:

1. Check if database schema migration is pending or failed
2. Verify that the skipped_query_count column exists in the discovery_runs table
3. Ensure application code and database schema are in sync

Review context

• Run timestamp: 2026-06-09T07:53:25.099219+00:00

• Run snapshot: state_repo/news_items/ingest/runs/2026-06-09T07-53-25-099219Z.json

• Debug summary: state_repo/news_items/ingest/logs/2026-06-09T07-53-25-099219Z.summary.json

• Debug log: state_repo/news_items/ingest/logs/2026-06-09T07-53-25-099219Z.json

• Workflow run: https://github.com/DataHackIL/tfht_enforce_idx/actions/runs/27191965769