Chaim
c7132ba0d2
All checks were successful
Build & Deploy / build-and-deploy (push) Successful in 9s
The "חלץ מטא-דאטה" / "חלץ הלכות" buttons in the UI used to only stamp the queue (set metadata_extraction_requested_at / halacha_extraction_requested_at) and rely on a human running `mcp__legal-ai__precedent_process_pending` from local Claude Code to drain it. That left the user with an unintuitive two-step flow: click button → run local MCP tool. Meanwhile, the upload endpoint already does the right thing — after ingest succeeds it calls `pc_wake_for_precedent_extraction`, which creates a Paperclip issue, assigns it to the CEO, and wakes them to run `precedent_process_pending` automatically. Add the same wakeup call to the manual request-metadata / request-halachot endpoints. Now clicking the button is sufficient — the CEO picks it up and drains the queue without manual intervention. Best-effort: matches the upload flow's failure semantics. The queue stamp still happens even if the wakeup fails, so the user can fall back to the manual MCP tool when needed. The wakeup outcome is included in the response under `wakeup` for observability. Coolify deploy required for the FastAPI container to pick this up.