Chaim
72c4593e74
All checks were successful
Build & Deploy / build-and-deploy (push) Successful in 1m27s
set_case_law_extraction_status and set_case_law_halacha_status now NULL the corresponding *_requested_at timestamp when status transitions to "completed" or "failed". Without this, completed rows kept lingering in the local-MCP work queue (which scans by `WHERE *_requested_at IS NOT NULL`) and the UI's isPrecedentActive check, leaving them undeletable until a manual SQL cleanup. The pre-existing process_pending_extractions path already called clear_extraction_request, but other paths (re-extraction, status set during upload) didn't — so the cleanup belongs at the status setter. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>