2 Commits

Include renames

Author	SHA1	Message	Date
woogiandClaude Opus 5	23e19f53b2	feat: review chat — ask the run why it concluded a finding ... Read-only Q&A on the review screen, per finding and per run, answered from the job's own artifacts (evidence, cluster, extraction, verification, Brain merge, sheet index, cover reconciliation, job.log). It never mutates findings, decisions, or the report. Turns are logged job-locally (review/chat_log.jsonl, transcript at /jobs/{id}/review-chat/log) and to a cross-job feedback store (REVIEW_FEEDBACK_DIR), which now also receives review decisions with their category/severity corrections. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0115gGtrSxXE9DKvS9XPFSoT	2026-09-14 10:35:18 -05:00
John Wilganowski	1c1d2ff21b	Add required human review gate to the Agent pipeline. ... Agent web jobs now stop after Brain consolidation and enter needs_review with a persisted review queue (blocking: high-severity, low-confidence, sensitive-category findings; audit sample of clean clusters). Humans decide confirm/reject/unsure/needs_clarification via new review API and frontend queue; a finalizer applies decisions (rejections suppressed with reason codes), performs bounded targeted reruns for clarifications, drafts RFIs only for kept issues, and only then marks the job done and sends the final email. Two-phase email (review-required, then final report), per-decision feedback labels with redacted aggregate metrics, restart recovery from job artifacts, and CLI --no-review bypass. Classic pipeline unchanged. 65 non-LLM tests.	2026-07-28 19:23:57 +00:00