789cc273ee74399737d603ba905e4cf78bf53ebf
All checks were successful
Build & Deploy / build-and-deploy (push) Successful in 32s
The local MCP worker is supposed to NULL `*_extraction_requested_at` after a successful run, but in practice these timestamps linger. The previous isPrecedentActive logic treated any non-null timestamp as "still active", which left completed rows permanently undeletable. Now only "processing" status (or genuinely queued: pending + timestamp) counts as active. Once a row is "completed"/"failed", stale timestamps no longer block the delete button. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Description
AI Legal Decision Drafting System — MCP server, web upload, RAG search
Languages
Python
59.1%
TypeScript
37.4%
JavaScript
1.7%
Shell
1.2%
CSS
0.5%
Other
0.1%