fc3b6b6cae35bd2d84b6046836b18dfb6f5c2ca6
All checks were successful
Build & Deploy / build-and-deploy (push) Successful in 33s
After running the dual-mode halacha extractor on a real appeals committee decision (403-17), the pending-review tab surfaced 351 halachot in a single flat list — the chair correctly pointed out that this is unusable without grouping. Three fixes: 1. Group pending halachot by precedent (case_law_id). Each group shows the citation, court, date, level and item count; default state is collapsed so the chair picks one ruling at a time. Within a group, items still sort by confidence ascending so the doubtful ones surface first. J/K/A/R/E now scope to currently-expanded groups; toggling open auto-focuses the first item. 2. Translate the badges that were leaking English: rule_type values (`persuasive`, `interpretive`, `binding`, `application`, `procedural`, `obiter`) now render as Hebrew labels, and `confidence X.XX` becomes `ביטחון X.XX`. The card header no longer repeats the citation since it's already in the group header. 3. Strip Unicode bidi marks (U+200E/F/202A-E/2066-9) from displayed citations. Nevo PDFs and the upload form embed these in the case_number; they render as zero-width but visually push the text away from the right edge of the table cell. Also: hide the empty court line under the case name in the list (was rendering as a stray em-dash), and use a muted em-dash for empty date/level rather than blank/dash inconsistency across columns. 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%