fix(dashboard): resolve action_taken from audit log, improve UI
Rohit Patil
09a4647
cases_demo.json stores action_taken as null for all cases; the real
Razorpay data (order_id, notes_verified, tool, timestamp) only lives
in audit_log.jsonl. Dashboard and detail pages were reading only from
the cases JSON so Order ID, Notes Verified, Tool Used and Timestamp
always rendered as dashes.
Changes:
- _build_dashboard(): accept audit_map, fall back to audit record for
action_taken when case JSON has null; verified column now shows
coloured Yes/No instead of plain dashes
- dashboard(): build audit_map from audit_log and pass to _build_dashboard
- case_detail_html(): fall back to audit record for action_taken,
llm_narrative and llm_confidence_statement when case JSON has null
- Fixed broken footer anchor (was HTML-escaped, rendered as literal text)
- Case ID cells in table are now proper links; risk score bold; order_id
in monospace font
readme: full rewrite — clean UTF-8, accurate content, no encoding artifacts
Rohit Patil
279fada
- README.md: complete rewrite with all accurate information, no garbled
characters from old BOM/encoding issues. Adds BOUNDARY01 hard-case docs,
correct policy thresholds (25k), updated demo dataset stats (28 cases),
feature importance table, two-pass detection explanation.
- .gitignore: add final_summary.md and demo-day-runbook.md as local-only
- demo-day-runbook.md: removed from git (private, add to .gitignore)
- Also stage updated audit_log, cases_demo, eval_results from last run
demo-day: re-run Razorpay actions for new pipeline, regenerate audit log
Rohit Patil
eb8c956
CASE12 (RING11) auto_hold: order_TSgpEnWpkQmdUu, notes_verified=True
All 11 non-log-only cases: verified with real test-mode Razorpay order IDs
CASE09 (BOUNDARY01): log_only, no Razorpay action (correct)
28 audit entries: 1 auto_hold, 10 escalate, 17 log_only
demo-day: rebuild BOUNDARY01 as genuine hard case, fix evaluate.py threshold, regenerate pipeline
